search

The-Yak-Collective / yakcollective

The Yak Collective website & related automation.
17 stars 9 forks source link

Create "infrastructure" pages modeled after project pages #29

Open necopinus opened 4 years ago

necopinus commented 4 years ago

@vgururao on Discord:

General thought: we need a way to put infrastructure contributors on the website/member directory and feature their contributions. Can we overload the "project" ontology to represent key infrastructure pieces (website, newsletter, discord) as an ongoing project and simply list the people under them, with the lead person being the "project" lead?

We wont have an artifact to feature, but for each, we can make a nice icon-hero image, and give it a title and description. Like the website could be "Yak Collective Website: An ongoing project to use cutting edge static-web page techniques within the Jekyll framework and Netlify" with a block diagram showing our setup as a hero image. @Nathan Acks (US Mountain) would be listed as project lead. If desired/where applicable, we can make the process material an open-source output (eg. the YC website code can be GPLed and made available for others to copy)

I don't think the design needs any change... at best we can clone the "project" page model as a "process" page model since infrastructure work doesn't have an end-date

Stuff I think fits the model: website, email newsletter, social media accounts, CFP process, discord admin, roam admin, chat schedule...

The benefit of making each of these infrastructure elements a featured contribution node is that it encourages innovation on process in addition to output, and makes the whole thing very transparent

All these infrastructure projects could live on a separate infrastructure home page as an index, same as the projects. Upcoming infrastructure efforts could be featured too.

necopinus commented 4 years ago

Maybe have this live under the "About" menu? Possibly related to #22.

vgururao commented 4 years ago

Update on this: on the Aug 1 infrastructure chat, we started working on a state-of-the-union deck to be continuously maintained and periodically presented (quarterly/annual). The organization of this deck is based on the unit of "cell" where a cell is any well-defined project OR infrastructure type activity. I think (but am not sure) that cell is the base class for this feature. Keep an eye on our deck as you develop this.

necopinus commented 4 years ago

Areas:

  1. Website
  2. Newsletter
  3. Marketing
  4. Plumbing (needs a better name, maybe should subsume website)
  5. ???

Venkat on Discord sez:

Current list of infrastructure projects: website v 2 or 3 or whatever it is currently, outbound newsletter, inward email alerts, CFP process v 2.0, marketing funnel (unstaffed), twitter bot 2.0...

List of steady state projects/processes not currently being version-upgraded: set of voice chats, Roam admin/editorial, Discord admin, google account, calendar+calendar bot...?

tilnow commented 4 years ago

i would explicitly also add the ongoing processes, like newletter too. i think, YC should have two types of recognitions: things done inwards (you can call them infra structure, but they need not be IT) and things done outwards. the reason i have is not because i think they are intrinsically different re importance, marketability, etc., but rather because i want to encourage the outwards looking projects and not dilute them with inwards activity.