-
Notifications
You must be signed in to change notification settings - Fork 1
Have governance #9
Comments
It may continue to be for a while, the reason I created this is because there is too much bureaucracy to get things changed on the Apereo site.
I'd like for it to be a sponsored project, but am not familiar with the project for getting official "sponsorship".
not yet
yes, and that will be documented soon
Not yet, maybe in the future, I'd prefer to go through a more streamlined process if possible. |
Initial committer documentation has been added https://github.com/ChristianMurphy/apereo.foundation/blob/master/.github/COMMITTERS.md |
I've contacted Ian Dolphin (Apereo Executive Director) to get the ball rolling for getting this project some form of official status. |
I've heard back from Ian. |
Is this communications review process related to
or a new initiative parallel to those initiatives? In lieu of? |
Not sure, my best guess is Oct 2017, July 2017, and this are all the same initiative. |
It's early, but this GitHub Pages site seems to be going well, and this is fun. Seems plausible that this site could look pretty compelling and viable by the time of a review. |
What is this? Is it a sponsored project? Does it have a PMC? Committers? Is it going through incubation?
I know what it is right now. Right now it's a personal repo in which some people who happen to be members of the community are, wearing their individual contributor hats, experimenting with a very promising, wonderful, potentially radically more welcoming and inclusive and effective way to wrangle the website. This is right and proper and good. Beautiful even.
And that might get pretty far along.
But not as far as it needs to go. At some point gotta wrestle down, no seriously, what is this, how is it governed, what makes it legitimate, how does it relate to Apereo the corporation. Can Apereo's website / webmaster spend be applied to work in this context? Etc.
Cf. https://github.com/apereo/apereo.github.io/issues/22
The text was updated successfully, but these errors were encountered: