Consolidate User Registry and Establish Processes for Keeping it Up to Date

Đang mở
#340 8 bình luận 3 reaction 2 người được giao Xem trên GitHub

@pkafei đang làm issue này rồi.

Từ ngày 19/11/2018.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

wg-agenda

Background

Piece: awesome-ipfs
We have also had the awesome-ipfs repo for years, where people can submit their own projects (read the contribution instructions at https://github.com/ipfs/awesome-ipfs#contribute-to-this-list), but that repo is not broadly publicized and has been intermittently used. It became much more useful and compelling when @hacdias and @VictorBjelkholm made awesome.ipfs.io -- a site that renders the info from awesome-ipfs as a website that you can browse through.

Piece: User Registry in Airtable
In early 2017 @mishmosh created an initial version of the IPFS User Registry in Airtable [Note: this document isn't public. This note discusses why, and points to solutions.]. It's designed to be a more complete user registry than awesome-ipfs, with additional information about those users' needs, their location along the adoption curve, etc. It has been a useful resource for some teams but we never pushed to make the list of users complete and the sheet hasn't gotten broad adoption from the teams who could use this info.

Piece: Google Forms experiment
In the leadup to the 2018 Developer Meetings we ran an experiment with Google Forms, using a User Registry entry form to gather more detailed information for the User Registry. About 40 projects submitted information there. The information was useful for prioritizing applicants who wanted to attend the developer meetings but we don't think people will be inclined to keep filling out a form like that on an ongoing basis -- we have gotten better results with awesome-ipfs.

Putting them Together
These three lists of IPFS Users have never been consolidated anywhere. There are definitely overlaps, but there are also many projects that appear in one place but not the others. There are also a huge amount of users who we know about but haven't listed in any of these places.

  • It definitely makes sense to keep using awesome.ipfs.io and encouraging people to enter their info into awesome-ipfs.
  • The working groups and product owners need a way to also track additional information about some users (ie. if they tell us privately that they're preparing for a big launch, or if someone reaches out privately about possibly adopting IPFS)

What to do

  • Confirm that we will use awesome-ipfs as the venue for publicly listing IPFS users. Promote it and update awesome.ipfs.io as necessary (ie. add ability to feature projects)
  • Choose where to track an internal copy of this User Registry (ie. should we keep using the airtable?)
  • Consolidate the information, making sure the internal registry is complete and making sure awesome-ipfs reflects a resonably complete listing of publicly known projects
  • Define processes for keeping the User Registry up to date

ref #218

Ngôn ngữ chính
Shell
Star
428
Fork
220
Chỉ số merge pull request
Không có pull request nào được merge trong 30 ngày

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của ipfs/community

Tất cả issue của ipfs/community

Issue tương tự

Thêm issue về Shell/Bash

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.