freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discussion] Structure of GitLab project


From: Albert Astals Cid
Subject: Re: [Discussion] Structure of GitLab project
Date: Sun, 23 Aug 2020 19:00:27 +0200

El diumenge, 23 d’agost de 2020, a les 18:36:17 CEST, Anurag Thakur va escriure:
> 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.

Let me suggest:

9. Determine which of the merging strategies you want to use, i.e. which of 
these 3 the project wants to use

https://i.imgur.com/Ev6AYuy.png

Cheers,
  Albert

> 
> 
> 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
> 







reply via email to

[Prev in Thread] Current Thread [Next in Thread]