On Friday, March 9, 2018 at 3:09:31 PM UTC+1, Ivan Mitev wrote:
> On 03/09/2018 02:53 PM, Yuraeitha wrote:
> > 
> > Suppose I'll start the first piece of the list to increase the individual 
> > github awareness. Where that list is later maintained or kept can be 
> > changed as we discuss that later. Please add your github if interested, and 
> > copy/paste the list to your own mail response here. Being on this list does 
> > nothing except increase awareness of who takes part in the Qubes community 
> > guides, there will be no expectations in turn, those who are busy will not 
> > become more busy from it unless wishing for it. <--- be warned it might add 
> > activity to your github page page though.
> > 
> > It doesn't matter if you prefer to work alone or in collaboration with 
> > others. This is also an opportunity to increase awareness of your work. The 
> > list strictly only purpose is just that, awareness, while work-style is a 
> > separate matter.
> > 
> > Knowing about someone's github account does not justify putting it on the 
> > list, please sign up for it so that we don't put anyone on who does not 
> > want to be on it. A simple search can show many Qubes OS wiki's, like 
> > https://github.com/search?utf8=%E2%9C%93&q=qubes+os&type=Wikis however it's 
> > not the same as agreeing to be on an awareness/promotional list.
> > 
> > A small description/introduction can be added to the list later, or now if 
> > you like to do that. Please keep it short though if you do, i.e Twitter/SMS 
> > post size description, slightly bigger than that should be okay though. The 
> > idea here is that introduction/descriptions can be updated later.
> > 
> > Copy/paste the list here (ABC) if possible.
> > Yuraeitha - https://github.com/Aekez - Right now not much has been done, 
> > however QubesTV is starting to take shape. Other repositories are currently 
> > work-in-progress.
> 
> * Yuraeitha - https://github.com/Aekez - Right now not much has been done,
>  however QubesTV is starting to take shape. Other repositories are
>  currently work-in-progress.
> * awokd - @awokd - mostly forks of qubes repos, no scripts
> * ivan - @taradiddles - qubes-os repo: app popup (increases
> productivity) + improving power management (script + deploying TLP)
> 
> 
> Finally, who will create the public wiki + the repo and assign rights ?
> You ? awokd ?

awokd posted same time as I was typing, so I'll edit to cover both responses. I 
agree we should protect this project from going rogue, conflicting interests 
outside the projects set goals, etc. 

Maybe Andrew can take the ownership, assign some of us to have maximum access. 
Then it's kept protected, without the Qubes Staff having to do anything beyond 
assigning new head moderators, which probably will be rare anyway. The head 
moderators can then assign sub-moderators (is that possible on github though?). 
But at the same time it also means the Qubes staff becomes owners, and it's 
uncertain if they want that? I agree it would be ideal from our perspective 
though, but would they want it?

I don't mind putting in the work for this project, I can enjoy it so it won't 
feel like a burden to me to do it, but it's also fine if others want to do it. 
We can probably organize it with a few people together as well. 

What about creating an Organization group on GitHub? the free version, at least 
at first. Quote: "Organization accounts allow your team to plan, build, review, 
and ship software — all while tracking bugs and discussing ideas."

Are there any redundancy in place for such an organization though? For example, 
can split ownership/leadership be made possible/easy on it? If no none knows 
then we can just try make one and experiment with it. It's probably best we 
find a way to secure the community stays healthy.

A GitHub organization also require a name, what should we call it?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e94ae542-72e4-4186-9804-0dfe4040738d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to