On Friday, March 9, 2018 at 4:04:00 PM UTC+1, Ivan Mitev wrote:
> On 03/09/2018 04:58 PM, Yuraeitha wrote:
> > 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 ?
> > 
> > Found this; 
> > 
> > Organizations include:
> > - A free plan with unlimited collaborators on unlimited public repositories
> > - The option to upgrade to paid plans with unlimited private repositories, 
> > sophisticated user authentication and management, 24/5 support, and a 
> > service level agreement for uptime availability
> > - Unlimited membership with a variety of roles that grant different levels 
> > of access to the organization and its data
> > - The ability to give members a range of access permissions to your 
> > organization's repositories
> > - Nested teams that reflect your company or group's structure with 
> > cascading access permissions and mentions
> > - The ability for organization owners to view members' two-factor 
> > authentication (2FA) status
> > - The option to require all organization members to use two-factor 
> > authentication
> > 
> > Source: 
> > https://help.github.com/articles/differences-between-user-and-organization-accounts/
> 
> I was looking at the same stuff:
> 
> https://git-scm.com/book/en/v2/GitHub-Managing-an-organization
> 
> If you're OK, create an organization and then if everything works out in
> the long run you can give the credentials to Andrew (I'm not sure he
> wants to take ownership, at least for now).

Works for me, I'll only keep it for the sake of getting the project running, I 
won't actual own it. I also prefer if a Qubes staff member takes it over, but 
we'll see what happens.

Name changes seems easy too, at least if not too many project links has been 
created. https://help.github.com/articles/renaming-an-organization/
So we can take our time to settle on a name. 

I'll use something default sounding as the initial name, "Qubes Community 
Collaboration". 

Here's the link
https://github.com/Qubes-Community-Collaboration

I invited you both as owners, so you have administration access as well.

-- 
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/02d27b54-e7b2-4544-827c-91cdf149bce8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to