Replies: 8 comments 5 replies
-
|
Sounds good to me, and I will of course be happy to join the team. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Sebastian! This all looks good to me and, as previously communicated, I'm happy to volunteer for this. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have time currently to do day to day work on |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @awvwgk! And to be clear, anybody (maintainer and non-maintainer alike) can be part of all design discussions and decisions. |
Beta Was this translation helpful? Give feedback.
-
Sorry for being unclear here. I was more thinking about setting priorities for features to develop or defining milestones, like being able to build class of projects, which would fall under a near future roadmap. I think this is an essential freedom for project maintainers to have. Of course, all design discussions and decisions will happen publicly and are open for everybody to participate in as before. |
Beta Was this translation helpful? Give feedback.
-
|
@awvwgk, @milancurcic in your mind, what exactly is the role of the maintainers? It looks like we all agree that anybody can be involved in discussions and decisions. We probably would agree that anybody can be involved with sending PRs and reviewing PRs. In terms of contributors, say over the last 8 months (from January 1, 2021), the top 4 are: @LKedward, @urbanjost, @awvwgk and @brocolis. The order stays the same over more recent periods. In terms of decision making, it seems there wasn't a problem so far for more day to day activities. For big issues like It seems the main need is to get reviewers for day to day activities, and also somebody who is willing to have a vision and lead the development. Somebody (team) that we trust to be able to keep the ball rolling and ensuring the community would agree with the major decisions. Small things can always be fixed. |
Beta Was this translation helpful? Give feedback.
-
|
Pulling the thread a little more:
It seems those should be the people who actually contribute code, so the 4 above (or more) that I mentioned. One idea from Linus Torvalds is that the person who does the work decides about how it gets done. Obviously, we must trust each other that we don't screw things up and that we will reach for the community for big design questions. But in terms of priorities, at the end of the day, what gets done depends on who submits the PRs. The roadmap is something that helps to motivate. And hopefully people who work on the project share the vision. :) |
Beta Was this translation helpful? Give feedback.
-
|
Please, let's not start counting commits here, there is no point. Contributions to fpm were never limited to code contributions only. The issue tracker and this discussion board as well as the discourse were always an integral part of the development of fpm with many great contributions to this project, which are not captured in GitHub's contributor metric at all, because it is limited to commits and LOC changes only. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, every metric is imperfect. We can count issue tracker contributions, you can use this tool: https://fortran-lang.org/community/, from January that would be @awvwgk, @LKedward, @urbanjost and @milancurcic. A pattern emerges. Given this, I would suggest @urbanjost to join the maintainers team also. We should be inclusive in setting up these teams, and one way to ensure that frequent contributors are included is by finding them with such metrics, as imperfect as they individually are. (Of course I agree and have always advocated for contributions to being defined broadly.) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, of course, John @urbanjost has been a core contributor and developer for fpm. I hope to have him on board with this as well. We should take some time here and make sure everybody gets a chance to comment in this thread. There is no need for hurry. |
Beta Was this translation helpful? Give feedback.
-
This is still open for discussion in way. A few points I find particular important are
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, I think I can agree on that. |
Beta Was this translation helpful? Give feedback.
-
|
I've updated the @fortran-lang/fpm team, this team can now be pinged and requested reviews from. |
Beta Was this translation helpful? Give feedback.
-
We have been discussing to form a maintainer team for fpm in a couple of discussions already.
I linked the relevant ones here:
To move this forward I suggest to take the following steps
this allows tagging
@fortran-lang/fpmor similar in issues or PRs(I think there is already a @fortran-lang/fpm-developers team around)
I have the feeling that with fpm we already have a team of de-facto maintainers here.
The thing that would essentially change for us, is how we steer the development of fpm and set goals for the project.
Let me know what you think.
Beta Was this translation helpful? Give feedback.
All reactions