welcome: please sign in

Diff for "RobinTempleton"

Differences between revisions 1 and 77 (spanning 76 versions)
Revision 1 as of 2011-02-23 01:40:58
Size: 932
Comment: new page
Revision 77 as of 2024-06-08 21:22:47
Size: 3063
Comment: remove "gandi" from domain-purchase service idea (significant recent price increases)
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== 2010 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, 2022--present
Line 5: Line 6:
 * 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. == Contact ==
Line 7: Line 8:
 * Move HCoop accounts to the National Cooperative Bank or a similar credit union.  * IRC: `robin` on Libera Chat
 * Email: `robin@terpri.org`
 * Mastodon: `@lispwitch@octodon.social`
Line 9: Line 12:
 * Implement a strong environmental policy when we are financially able to; purchase carbon offsets to compensate for our use of nonrenewable energy. == Tasks ==
Line 11: Line 14:
 * 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. {{{
<robin> i will personally commit to making a tinkerable "hcoop-in-a-box" in 202[45], depending on the work situation [...]
}}}
Line 13: Line 18:
 * Last but not least, I will have HCoop T-shirts printed, finishing the project that NathanKennedy began in 2005. (:  * Jitsi Meet support
 * ActivityPub-based libre social networking system (e.g., Mastodon, Pleroma/Akkoma, misskey, etc.; there are other AP-based services like bookwyrm,
 * 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
 * ''in progress:'' Implement client-side HCoop integration under Guix System (openafs package and service completed)
 * Help resolve the WikiReplacement2021 situation
 * Automagic LetsEncrypt integration: ideally make it entirely automatic and enabled by default

== *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 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
 * Kerberos 2FA support?
 * Single sign-on for hcoop.net services? (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
 * Evaluate other bug reporting/ticketing systems like osTicket and debbugs (the latter is used for both Debian and GNU packages)
 * Application link is not ''nearly'' obvious enough on the homepage
 * Apparently for email we should have not just SPF but also DKIM (which is way more complicated)
 * Review [[https://pad.drutopia.org/p/libresaas|LibreSaaS list]]
 * Debug wiki list CSS: links in items cause additional whitespace

----
CategoryHomepage

HCoop member since 2005; served as Secretary 2011--2018, 2022--present

Contact

  • IRC: robin on Libera Chat

  • Email: robin@terpri.org

  • Mastodon: @lispwitch@octodon.social

Tasks

<robin> i will personally commit to making a tinkerable "hcoop-in-a-box" in 202[45], depending on the work situation [...]
  • Jitsi Meet support
  • ActivityPub-based libre social networking system (e.g., Mastodon, Pleroma/Akkoma, misskey, etc.; there are other AP-based services like bookwyrm,

  • 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
  • in progress: Implement client-side HCoop integration under Guix System (openafs package and service completed)

  • Help resolve the WikiReplacement2021 situation

  • Automagic LetsEncrypt integration: ideally make it entirely automatic and enabled by default

*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 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
  • Kerberos 2FA support?
  • Single sign-on for hcoop.net services? (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

  • Evaluate other bug reporting/ticketing systems like osTicket and debbugs (the latter is used for both Debian and GNU packages)
  • Application link is not nearly obvious enough on the homepage

  • Apparently for email we should have not just SPF but also DKIM (which is way more complicated)
  • Review LibreSaaS list

  • Debug wiki list CSS: links in items cause additional whitespace


CategoryHomepage

RobinTempleton (last edited 2024-06-19 01:21:49 by ClintonEbadi)