You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But what's more interesting and challenging question: how will we proceed with new feature requests or suggestions? Typically, such tickets require deeper understanding of the project compared to implementation-only concerns. WDYT?
From my point of view, requests for new features will have to wait (and be marked as pending or some such) until there is a dedicated group of maintainers in place. clj-commons does, as of now, not have the capabilities to evolve a project like aleph.
So I guess a (to me) more interesting discussion would be how to ensure that such a group is in place, and also how we ensure that such a group consists of the right people.
On a side note, I hope it's ok that I started this discussion here in, well, discussions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@kachayev wrote over in issues (#555):
From my point of view, requests for new features will have to wait (and be marked as
pending
or some such) until there is a dedicated group of maintainers in place. clj-commons does, as of now, not have the capabilities to evolve a project like aleph.So I guess a (to me) more interesting discussion would be how to ensure that such a group is in place, and also how we ensure that such a group consists of the right people.
On a side note, I hope it's ok that I started this discussion here in, well, discussions.
Beta Was this translation helpful? Give feedback.
All reactions