|
Size: 2208
Comment: more sysadmins, gsoc 2012
|
Size: 1589
Comment: more stuff
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == 2011 Board Statement == | ## page was renamed from BtTempleton #pragma section-numbers off |
| Line 3: | Line 4: |
| I have been a member of HCoop since 2005; I wrote the Domtool Emacs mode, was involved in the 2009 migration project, started the hcoopstatus Identica group, and am redesigning the member portal. My platform: | HCoop member since 2005; served as Secretary 2011--2018 |
| Line 5: | Line 6: |
| * Plan to expand to 150--250 members during the next year. End the pledge system once we can do so without increasing dues significantly. | == Top priorities == |
| Line 7: | Line 8: |
| * Move HCoop accounts to the National Cooperative Bank or a similar credit union. | * Jitsi Meet support * Mastodon or a similar libre social networking system * Matrix or a similar libre text-chat system (maybe; at least we have IRC) * Package (finish packaging) HCoop software for Guix to make it easier for non-sysadmins to experiment * Implement HCoop integration under Guix System (openafs service, etc.) |
| Line 9: | Line 14: |
| * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy. | == *scratch* == |
| Line 11: | Line 16: |
| * Document development processes for our custom software. Recruit more volunteers for system administration tasks. Consider applying to be a mentoring organization for Google Summer of Code 2012. | * Allow use of GNU Guix on HCoop (provided that resource requirements are not too high) * Informally federate with other hosting coops and collectives? Perhaps go further and informally federate with workers coops as well? * Better domtool usability; perhaps eldoc integration, a GUI/form-based interface to (a subset) of the language, etc. * Become a small-scale Gandi domain reseller? (easy "buy and add a domain" system for portal) * Better voting system for board elections (ranked-choice, etc.)? Purely a theoretical issue right now * Try out some gitweb alternatives, like sourcehut * Kerberos 2FA support? * Single sign-on for hcoop.net websites? (not kerberos-based although that's theoretically possible, due to lack of browser support) * Disable wiki captchas for logged-in users * Try out account renaming * Licensing policy (libre licensing for software and official documentation) * Contemplate new/adjusted logo design * Website design tweaks * Sieve support for roundcube * Discuss possible uses of a surplus |
| Line 13: | Line 32: |
| * Last but not least, I will have HCoop T-shirts printed, finishing the project that NathanKennedy began in 2005. (: == 2010 Board Statement == I have been a member of HCoop since 2005; I wrote the Domtool Emacs mode, was involved in the 2009 migration project, started the hcoopstatus Identica group, and am redesigning the member portal. My platform: * Plan to expand to 150--250 members during the next year and then end the pledge system once we can do so without increasing dues significantly. * Move HCoop accounts to the National Cooperative Bank or a similar credit union. * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy. * Document development processes for our custom software and recruit a fourth admin. Also consider making it possible for admins to delegate certain tasks to trusted non-admins. * Last but not least, I will have HCoop T-shirts printed, finishing the project that NathanKennedy began in 2005. (: == OpenID server == Would it make sense for HCoop to be an OpenId provider? [[http://pypi.python.org/pypi/gracie/0.2.6|Gracie]] is a server that authenticates users using PAM, and it's in Debian. We could allow users to register their identity URIs using domtool, as well as supporting `http://hcoop.net/~user` automatically. |
---- CategoryHomepage |
HCoop member since 2005; served as Secretary 2011--2018
Top priorities
- Jitsi Meet support
- Mastodon or a similar libre social networking system
- Matrix or a similar libre text-chat system (maybe; at least we have IRC)
- Package (finish packaging) HCoop software for Guix to make it easier for non-sysadmins to experiment
- Implement HCoop integration under Guix System (openafs service, etc.)
*scratch*
- Allow use of GNU Guix on HCoop (provided that resource requirements are not too high)
- Informally federate with other hosting coops and collectives? Perhaps go further and informally federate with workers coops as well?
- Better domtool usability; perhaps eldoc integration, a GUI/form-based interface to (a subset) of the language, etc.
- Become a small-scale Gandi domain reseller? (easy "buy and add a domain" system for portal)
- Better voting system for board elections (ranked-choice, etc.)? Purely a theoretical issue right now
- Try out some gitweb alternatives, like sourcehut
- Kerberos 2FA support?
- Single sign-on for hcoop.net websites? (not kerberos-based although that's theoretically possible, due to lack of browser support)
- Disable wiki captchas for logged-in users
- Try out account renaming
- Licensing policy (libre licensing for software and official documentation)
- Contemplate new/adjusted logo design
- Website design tweaks
- Sieve support for roundcube
- Discuss possible uses of a surplus