-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a Sigstore Landscape #818
Comments
Please let me know what info is need when and I'll start to pull it altogether! |
Hi, @tracymiranda |
please ensure it's in an openssf owned repo end of day
…On Wed, Apr 13, 2022 at 7:19 AM Andrey Kozlov ***@***.***> wrote:
Hi, @tracymiranda <https://github.com/tracymiranda>
Create a new repo, for a start, and add me as a collaborator to the repo.
—
Reply to this email directly, view it on GitHub
<#818 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSIN55DFR756VMOHUXMLVE23WLANCNFSM5TKOPVFA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Cheers,
Chris Aniszczyk
https://aniszczyk.org
|
@AndreyKozlov1984 repo is here and you should have access: https://github.com/sigstore/landscape |
Ok, that is great! @caniszczyk just to make it clear, this will be its own landscape, because if we want to have a new tab in OpenSSF landscape, we would better start there. But if we want its own guide, an independent landscape is the best option, and we can give a link from one landscape to the other from OpenSSF |
My preference is to do this as a tab in the openssf landscape:
https://landscape.openssf.org
Like we have the serverless tab/landscape in the CNCF landscape.
…On Thu, Apr 21, 2022 at 5:03 AM Andrey Kozlov ***@***.***> wrote:
Ok, that is great! @caniszczyk <https://github.com/caniszczyk> just to
make it clear, this will be its own landscape, because if we want to have a
new tab in OpenSSF landscape, we would better start there.
But if we want its own guide, an independent landscape is the best option,
and we can give a link from one landscape to the other from OpenSSF
—
Reply to this email directly, view it on GitHub
<#818 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSIJSN3DKW74NYXHBVN3VGERXLANCNFSM5TKOPVFA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Cheers,
Chris Aniszczyk
https://aniszczyk.org
|
@tracymiranda @caniszczyk then here is what I'm going to do: Regarding guide, right now the guide supports only the main landscape, but there are no reasons why it can not support an extra tab. Is that fine? |
+1
On Thu, Apr 21, 2022 at 12:40 PM Andrey Kozlov ***@***.***> wrote:
@tracymiranda <https://github.com/tracymiranda> @caniszczyk
<https://github.com/caniszczyk> then here is what I'm going to do:
In an OpenSSF landscape I'll make a new branch. There I'll add a new tab,
called "SigStore" and will create a new category with subcategories to fill
it. And will add few items for a start.
Regarding guide, right now the guide supports only the main landscape, but
there are no reasons why it can not support an extra tab.
Is that fine?
—
Reply to this email directly, view it on GitHub
<#818 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSIMMSKR4SMPDU457QITVGGHKNANCNFSM5TKOPVFA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Cheers,
Chris Aniszczyk
https://aniszczyk.org
|
SGTM, if we can still have the guide and meet the stated goals then I don't mind where this lives. |
@tracymiranda sorry for the delay, I started to put everything here, For each item in your sketch I need a homepage_url, github_url, icon, name and a crunchbase entry. I'll try to find this myself when it is something trivial. Regarding the guide - let's start it right now, give me any text, better in a markdown, and I'll try to convert it to the guide. Feel free to contact me in slack or here, I'm going to get this tab populated today |
🎉 this is pretty sweet, thank you @AndreyKozlov1984. Here's a fwv of a guide we can use (see below), let me know if this format works. I'll start to gather up the links and icons for the rest of the landscape.
|
(just updated the comment to make sure the markdown shows up properly) |
Great, that would be a good start. We have maximum one guide per website, but so far OpenSSF does not have any guide. I'll add your guide soon |
Ack - we can integrate this guide into a main one when openssf get to that stage. Here are details of 2 entries in the 'signed-by' category:
I'll aim to do the same for other categories next week. Please let me know if any questions. |
Thank you, all looks fine now, please provide more details for other categories, if you know that a certain item exist in other landscape, I'll just copy it from there, and will add extra fields like 'How to verify' Regarding the guide, will update you later today, so far no issues |
@tracymiranda I've added a guide |
Thanks @AndreyKozlov1984 - is there a new link to see the deploy preview? Also we now have the Sigstore logo for one entry: Please let me know if I should submit a pr anywhere or if that is enough info to add it in. (Subproject logos still in progress...) |
We now have the logos ready for the subprojects. There are four entries:
If we need a crunchbase entry, then we'd use the parent one of sigstore: https://www.crunchbase.com/organization/sigstore |
Great, @tracymiranda , I'll update you after I add these entries |
Work in progress, the goal is to create a new tab for cncf/landscapeapp#818 Signed-off-by: Tracy Miranda <[email protected]> Co-authored-by: Andrey Kozlov <[email protected]> Co-authored-by: Tracy Miranda <[email protected]>
Sigstore is a project that is part of OpenSSF. This landscape would represent Sigstore's ecosystem (and eventually be embedded in the OpenSSF main landscape). Goals for the landscape:
Ideally l.sigstore.org would be hosted at https://github.com/sigstore/sigstore-landscape
It should include a guide in the first version
The initial layout is loosely based on l.graphql.org
Here's a sketch:
The text was updated successfully, but these errors were encountered: