search

ipfs / ipfs-gui

Creating standards and patterns for IPFS that are simple, accessible, reusable, and beautiful
105 stars 17 forks source link

Move this repo to ipfs-shipyard and make it public? #19

Closed daviddias closed 6 years ago

daviddias commented 6 years ago

Hi all! I'm thinking that now that a team is assembled and we have identified goals, it is a good time to move this repo into the open so that others can subscribe to it. What do you think?

lidel commented 6 years ago

Makes sense. If we continue in private mode we risk duplication of effort (that was my feeling during the last in-web-browsers OKR meeting, where not everyone was on the same page).

Something to note: we have some external resources (google doc, zeplin) that are relevant to this effort. What will be the policy for accessing them? On-request?

daviddias commented 6 years ago

(that was my feeling during the last in-web-browsers OKR meeting, where not everyone was on the same page).

True, felt the same. Let's have in mind, however, that the IPFS GUI project is one of many endeavors from IPFS In Web Browsers Working Group, just like ipfs-companion, ipfs-station, ipfs-webui and others to come, each with its set of goals and which some overlap or share.

On docs access policy. I think that we can enable read access by URL to Google Docs, for Zeplin we will be limited but they also will be less requested, we can consider the case by case basis.

hacdias commented 6 years ago

Yup, I agree with both of you. If we make this public, it will be easier for people who want to contribute to know what there is to do and to keep the goals focused.

lidel commented 6 years ago

@diasdavid seems to be done – can you close this one? (I would do that, but I don't see the button, probably lacking permissions still)

daviddias commented 6 years ago

@lidel fixed the permissions issue :)