So, with the issue porting nearly done, I would like to start a discussion about the structure/workflow of the gitlab project.
So, Here are some of my suggestions/questions: 1. Rename the git project from freetype2 to freetype(i.e. Use gitlab.com/freetype/freetype instead of gitlab.com/freetype/freetype2) 2. Determine a workflow for the project.(Check if the "git flow" workflow would suit the project) 3. What should be the format of "new issue" template on gitlab? 4. What should be the format of "new merge request" template on gitlab? 5. How would the commits be structured in an MR?, will the commit title follow a naming convention? 6. Determine the permission level for each contributor.(Who are the owners, maintainers, developers etc., Do we set an yearly limit on access, hence automatically removing access for inactive accounts?) 7. Determine the labels available to be applied to issues. 8. Determine the function, permission level of freetype-bot in the short as well as long term. I want to make sure that the switch to gitlab enhances productivity, improves community interaction, decrease friction for potential contributors and leads to a better product in the long run 😊. Everyone please send your suggestions/opinion🙏 Regards, Anurag
