|
Size: 3355
Comment:
|
Size: 1132
Comment: miscellaneous additions
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| HCoop user bpt; member since 2005, Secretary 2011--present | HCoop member since 2005; served as Secretary 2011--2018 |
| Line 6: | Line 6: |
| == OpenID server == | == Top priorities == |
| Line 8: | Line 8: |
| 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. == Hosting notes == Peer1: 1/4 rack of space (~4U used?), 5Mbps bandwidth (95th percentile billing), IPv6 available in the data center but not set up for our account, remote hands cost $25 for minor tasks in 2013 |
* Jitsi Meet support * Mastodon or a similar libre social networking system * 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 16: | Line 15: |
| 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. Provide more VCS web interfaces: eventually we should have some subset of darcshub, darcsweb, hgweb, gitorious, cgit, extended gitweb, maybe even Sourceforge or Savane (or, as of 2016, Gitlab/Kallithea/gogs/...) 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 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]] Moniker TODOs: Keep changes in version control. Reduce wasted white space at top of page. Center HCoop logo. 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 be GPL-compatible since we probably have some "content" that is GPL, like domtool docstrings. (CC-BY-SA 4.0 is one-way compatible with GPLv3.) 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 [[https://utcc.utoronto.ca/~cks/space/blog/web/TLSSuicideAndUserCGIs|One good reason not to allow .htaccess:]] it's apparently difficult to control which HTTP headers can be set by users |
* Allow use of GNU Guix on HCoop (provided that resource requirements are not too high) * Informally federate with other hosting coops and collectives? * 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? * Disable wiki captchas for logged-in users * Try out account renaming |
HCoop member since 2005; served as Secretary 2011--2018
Top priorities
- Jitsi Meet support
- Mastodon or a similar libre social networking system
- 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?
- 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?
- Disable wiki captchas for logged-in users
- Try out account renaming