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
As discussed previously with some members of the community, Mainframe is currently focusing on other projects than MainframeOS, which has been the main driver for our work on Erebos.
Considering Erebos is also used by other members of the community, I'd like to make sure it can continue to evolve and serve the wider Swarm community beyond Mainframe's involvement.
The first step in my opinion would be to grant write access to this repository and the erebos organization on npm to make sure contributors can move the project forwards.
People I'm thinking about so far would be @nolash and @jpeletier for their Swarm expertise and @AuHau, @agazso and @vujevits for their code contributions if you are up for it, but if anyone has other suggestions please don't hesitate to share them!
Part of this discussion I'd also like to add contributing guidelines to make it easier for new contributors to get started, if you know of any good template or other suggestions, please share them here!
Thanks!
The text was updated successfully, but these errors were encountered:
I am happy to help as well :-) I would mainly propose to create CONTRIBUTING.md to help the people with different aspects of the contribution. But the resources from agaszso looks good as well.
I realized yesterday that because MainframeHQ is using a paid GitHub organization, it costs to add individual contributors so I'll try to move it to another open-source organization to avoid this limitation.
I'll try to make this change and add contributing guidelines in January but in the meantime if you want to open PRs for these please don't hesitate!
As discussed previously with some members of the community, Mainframe is currently focusing on other projects than MainframeOS, which has been the main driver for our work on Erebos.
Considering Erebos is also used by other members of the community, I'd like to make sure it can continue to evolve and serve the wider Swarm community beyond Mainframe's involvement.
The first step in my opinion would be to grant write access to this repository and the
erebos
organization on npm to make sure contributors can move the project forwards.People I'm thinking about so far would be @nolash and @jpeletier for their Swarm expertise and @AuHau, @agazso and @vujevits for their code contributions if you are up for it, but if anyone has other suggestions please don't hesitate to share them!
Part of this discussion I'd also like to add contributing guidelines to make it easier for new contributors to get started, if you know of any good template or other suggestions, please share them here!
Thanks!
The text was updated successfully, but these errors were encountered: