META: should this repo et al live in this GH org, Flashpoint-Artists-Initiative, or somewhere else?

[donaldguy]

As per my "manifesto" my goal, in undertaking this project this way¹, was with a view towards creating a codebase that can solve this problem into a time beyond a week and a half from now

For that to be the case, it muse be somewhere other relevant people can both find it and get the permissions they need on it.

Insofar as this code is interdependent (slightly) with other services, it would be good for those things to live together .

So! To repeat what I posted off-topic in #2 (comment) :

[On a meta level somewhere where relevant people might see it, if not technically where it belongs:

I only became aware belatedly of the existence of the Flashpoint-Artists-Initiative org.

...I'd be happy to normalize one way or the other (or indeed e.g. abscond to gitlab, I just want something more legible less for myself than for others who may follow in these steps in the future)]

(It does not appear that the public version in FPI (nor Jereds fork) is the active codebase for volunteer.; where is that living? What about for fireflyartscollective.org proper?)

So what say you, @jeredfloyd @JimAnkrom and relevant others not extremely clear to me?

(Which dovetails into a secondary question:

once we pick a place, who else should be looped in?, and/or (if we are at full compliment (for 2022)), what policies or measures can/should be taken to ensure Continuity of Control/Access²?

Footnotes

1. if indeed anyone believes this wasn't a product purely of emergent self-weaponized neuroticism ↩

2. there is for sure a military / intelligence abbreviation for this concept ... COMCONT or something; but whatever "bus factor" ↩

[jeredfloyd]

The current volunteer and ticketing software is in a private Bitbucket that Jesse Campbell maintains, and the SMART Health Card verifier that glues inelegantly in is in a GitHub project here. All of these have accreted over time and have significant challenges with brittleness, transparency, schema... in addition to being written in a mish-mash now of Perl, PHP, and Node.JS.

I have a Master Plan to build something over the next year that will be a general Burn Management System which can accept pluggable components, so I really suggest not spending too much time on aggregating the existing pieces.

Of course, I have intended to do this in the past many times and failed, mostly for want of deciding on the back-end project engine to use (Python/Flask, PHP/??, etc.) The SMART Health Card project made me get over a great deal of my hatred of JavaScript and Node, so that's the current leading contender.

Anyway, let's talk after the burn!

[donaldguy]

I hear you; I'm gonna post this cause the thoughts have been formulated, but I will drop the matter for (at least) 2 weeks:

• certainly if it would be a lot of work to resolve than it likely passes a threshold of utility

• but I also suspect merely having the disused/outmoded code in one centralized place (or at least accumulated into a navigable/hyperlinked index?) would also be useful for that effort

[JimAnkrom]

We do have a significantly large community of tech folk that could help with some efforts - the major; and I do want to stress, absolutely major, concern - will be identifying who's actually capable of both project management leadership and, separately, dev leadership, and having them direct the show. In my experience we've somewhat suffered from allowing people to operate in silo'd or even white wizard tower existence, and that has resulted in unmaintainable and entropy-prone applications. We can't really continue that direction and hope for success on either short or long term.

…

On Fri, Jun 24, 2022 at 10:06 PM Donald Guy ***@***.***> wrote: I hear you; I'm gonna post this cause the thoughts have been formulated, but I will drop the matter for (at least) 2 weeks: - certainly if it would be *a lot* of work to resolve than it likely passes a threshold of utility - but I also suspect merely having the disused/outmoded code in one centralized place (or at least accumulated into a navigable/hyperlinked index?) would also be useful for that effort — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABL3XA4UZL5ZMXZBFM3FVULVQZSQVANCNFSM5ZZMMAXQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[donaldguy]

I am moving out of the northeast in two weeks and probably unlikely to attend firefly again (and e.g. next year specifically probably even less so)

Never say never, but whereas y'all seemed uninterested in this project in the first place and my personal interest in it has been obviated, I am going to archive it to stop spamming my notifications with depandabot alerts

and resign the organization, make y'all owners; feel free to use or delete at your preference