|
Size: 4892
Comment:
|
Size: 2445
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from BtTempleton | |
| Line 3: | Line 4: |
| == 2011 Board Statement == | HCoop member since 2005; served as Secretary 2011--2018 |
| Line 5: | Line 6: |
| 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 [[http://hcoop.net/~bpt/hcoop/portal.html|redesigning the member portal]]. My platform: | == Top priorities == |
| Line 7: | Line 8: |
| * Expand to 150–250 members during the next year and end the pledge system. * 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. Recruit more volunteers for system administration tasks. Consider applying to be a mentoring organization for Google Summer of Code 2012. * Last but not least, I will print HCoop T-shirts, 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 [[http://openid.net/|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. |
* Jitsi Meet support * ActivityPub-based libre social networking system (e.g., Mastodon, Pleroma, etc. -- Twitter/FB alternatives) * Matrix or a similar libre text-chat system (maybe; at least we have IRC and XMPP) * Finish HCoop packaging for Guix to make it easier for non-sysadmins to experiment * Implement client-side HCoop integration under Guix System (openafs service, etc.) * Help resolve the WikiReplacement2021 situation |
| Line 37: | Line 17: |
| Gitweb URIs: Repo.or.cz uses cleaner URIs than gitweb's defaults -- for example, `/w/foo.git/commit/abcdef` for viewing an individual commit. We should patch our gitweb script to provide something similar. It might also be useful to host hgweb and darcsweb instances. At least one user wants to host mercurial repositories, and several of us use darcs. Next meeting: sign the [[http://www.internetdeclaration.org/|Declaration of Internet Freedom]] and register as a stakeholder in [[https://gnu.org/consensus|GNU/consensus]] Set up an independent MeetBot instance. Fix moinmoin headings somehow. Many pages use H1 for section titles which makes the outline (in the html5 sense) nonsensical and contradicts w3c recommendations Fix defaults that lead to serving the same resource from multiple URIs. In particular, don't serve files from `public_html` from domains by default, and use permanent redirects from the `www` subdomain to the bare domain name or vice versa Poll members about what they would like to do with free social networking services (e.g., ostatus, mediagoblin); what approaches they would prefer for vanity domains vs. central installations; use by non-members (e.g. will their friends want to use their installations, would their friends join hcoop, etc.); semi-managed installations vs. manual individual administration; ... Implement portal redesign: http://hcoop.net/~bpt/tmp/portal.html Go to FOSS Fair: https://opensource.ncsu.edu/FossFair2013 Research registered agents; Incorp requires that we use a proprietary, Windows-only Silverlight program to pay the annual fee Find out whether we can accept copyright assignments Pass [[https://lists.hcoop.net/pipermail/hcoop-misc/2008-February/000082.html|ntk's anti-FISA policy]] Policy/guideline ideas: Licensing policy: (A)GPLv3-compatible for software, the usual free content licenses for other things? We may want an exception for logos, or just protect them as trademarks like Debian does. The content license(s) should ideally be GPL-compatible since we probably have some "content" that is GPL (like domtool docstrings). Relicensing the wiki may be difficult, but there are probably not many (15, 20?) contributors of substantial amounts of currently-relevant text, excluding homepages. Internal writing guidelines: use gender-inclusive language; promote only FreeSoftware officially, and ask that people consider FreeSoftware principles and the SevenPrinciples when officially recommending a service or organization; write "GNU/Linux" instead of "Linux" when referring to the entire OS |
* Automagic LetsEncrypt integration: ideally make it entirely automatic and enabled by default * 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 or similar)? Purely a theoretical issue right now * Try out some gitweb alternatives, like sourcehut, gitile, .... Minimally a nicer gitweb-type browser would be good; it'd also be useful to have Github/Gitweb-style PRs, though there are probably issues (spam) with allowing that for contributions from non-members * Kerberos 2FA support? * Single sign-on for hcoop.net websites? (not kerberos-based due to lack of browser support under typical configurations, although that's theoretically possible, perhaps with a WebExtension...) * Disable wiki captchas for logged-in users, or verified users in a particular group * 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 * Integricloud offers POWER9-based hosting (presumably with RaptorCS hardware), but is expensive and probably not a good candidate for several other reasons * Rethink VolunteerResponsePolicy: consider ntk's comment on admin vs. operational response times, also perhaps ''require'' sysadmins to take some time off periodically |
HCoop member since 2005; served as Secretary 2011--2018
Top priorities
- Jitsi Meet support
ActivityPub-based libre social networking system (e.g., Mastodon, Pleroma, etc. -- Twitter/FB alternatives)
- Matrix or a similar libre text-chat system (maybe; at least we have IRC and XMPP)
- Finish HCoop packaging for Guix to make it easier for non-sysadmins to experiment
- Implement client-side HCoop integration under Guix System (openafs service, etc.)
Help resolve the WikiReplacement2021 situation
*scratch*
Automagic LetsEncrypt integration: ideally make it entirely automatic and enabled by default
- 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 or similar)? Purely a theoretical issue right now
- Try out some gitweb alternatives, like sourcehut, gitile, .... Minimally a nicer gitweb-type browser would be good; it'd also be useful to have Github/Gitweb-style PRs, though there are probably issues (spam) with allowing that for contributions from non-members
- Kerberos 2FA support?
Single sign-on for hcoop.net websites? (not kerberos-based due to lack of browser support under typical configurations, although that's theoretically possible, perhaps with a WebExtension...)
- Disable wiki captchas for logged-in users, or verified users in a particular group
- 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
- Integricloud offers POWER9-based hosting (presumably with RaptorCS hardware), but is expensive and probably not a good candidate for several other reasons
Rethink VolunteerResponsePolicy: consider ntk's comment on admin vs. operational response times, also perhaps require sysadmins to take some time off periodically