Plans on how do we maintain this project further?

[jenishngl]

Just wanted to check on the next plans for this fork

1. Do we need to rename this fork?
2. Do we need a new domain?
3. Do we have any regular meetings(bi-weekly or something like that)?
4. How do we list down the priority tasks for a fresh new release since this project is not updated for a while

[madc]

5. License (current and future)

[pixxet]

1. Fork Renaming: Renaming the fork isn't strictly necessary, but it might help to differentiate it from the original project. I would suggest handling this in our first regular meeting.

2. Domain Consideration: A new domain isn't a requirement at the beginning since we are trying to revive the project on the first step not create a new brand, but it could provide a dedicated identity to the fork. I would suggest delaying the creation of the brand once we are done with our first setup, i mean there are a lot of work to do to gather all needed information over the application and its backend at the beginning. once we decided to establish our own brand, a new domain could be very beneficial.

3. Regular Meetings: Regular meetings will enhance collaboration. but i'd rather go with Bi-Weekly for the first 3 months then later go for monthly meetings afterwards. this will help us discuss and accelerate the progress, upcoming tasks, and address challenges at the beginning.

4. Priority Task Listing: To prioritize tasks, follow these steps:

   • Review open issues and feature requests (also those in the original repository).
   • Create a list of tasks to give this repository own documentation and remove old links connected to crater.financial and craterapp.com
   • Assess community needs and user feedback.
   • Categorize tasks into "Critical," "High," "Medium," and "Low" priority.
   • Discuss the current tech stack and maybe redefine it if it's needed.
   • Create a roadmap for the next release, focusing on high-impact features and critical bug fixes.

5. Licensing:

   • Current License: GNU Affero General Public License v3.0
   • Future License: The GNU Affero General Public License (AGPL) v3.0 allows forking and modification. The AGPL is a strong copyleft license that ensures the freedoms of users to access, modify, and distribute the software, even if it's used over a network.
     However, we need to comply with the terms of the AGPL, which typically include:
     1. Providing the source code: If you distribute your modified version to others, you must also provide the corresponding source code for your modifications.
     2. Network interaction: If your modified version is used over a network, you must make sure that the users interacting with the software over the network have access to the source code of the modified version.
     3. Changes and notices: If you make changes to the code, you must indicate those changes in your modified version and provide appropriate notices in the code.
     4. Licensing of modifications: Any modifications you make to the code must be licensed under the AGPL v3.0 or a compatible license.
        This means, we cannot change the license of a project that is originally licensed under the GNU Affero General Public License (AGPL) v3.0 to a permissive license like the MIT or Apache license. The AGPL is a strong copyleft license that requires any derivative works to also be licensed under the same terms, ensuring that the source code remains open and freely available.

If we want to use a permissive license like MIT or Apache, we would need to start with a codebase that is already under one of those licenses or obtain permission from all contributors to the AGPL-licensed project to re-license their contributions.

It's important to respect the terms of the original license and the intentions of the original developers when working with open-source projects. We could attempt to contact the maintainer of crater. Financial and inquire about obtaining permission. However, I'm sceptical about the likelihood of this resulting in a positive outcome.

[pixxet]

Hi Team,

I hope this message finds you well. It's time for us to kickstart our collaborative efforts with our first regular meeting. This will be a crucial step in aligning our goals and setting the stage for productive discussions and contributions.

Meeting Agenda:

1. Project Overview: Briefly revisit the goals and objectives of our Crater fork project.

2. Roles and Responsibilities: Discuss and assign roles and responsibilities within the team.

3. Feature Prioritization: Review the priority tasks for our upcoming release and establish a roadmap.

4. Licensing and Compliance: Ensure a clear understanding of the AGPL v3.0 license and compliance requirements.

5. Communication Channels: Decide on the primary platform for our meetings and ongoing communication.

6. Next Steps: Summarize key action items and set expectations for our future engagements.

Meeting Details:

• Duration: 1 hour

Please come prepared with any questions, ideas, or concerns you may have. Your active participation will be essential as we embark on this journey to revive and enhance Crater.

Looking forward to our first meeting and the exciting work ahead!

[pixxet]

About 2 months later. Any participants ?

[Xsmael]

Looks like this isnt going anywhere

[pixxet]

It’s dead! I already started another project!

anyone who’s interested and serious about this project can take the lead.

I’ll go ahead and close this discussion l.

[Xsmael]

When you say another project, are you talking of something completely different or still crater related ?

[pixxet]

Unfortunatly completely different. I tried to give this project a chance and waited enough before giving up on it.