| 1 |
On Fri, Jun 26, 2020 at 01:40:27AM +0000, Max Magorsch wrote: |
| 2 |
> I, for one, do see the Gentoo Council as an opportunity to actively |
| 3 |
> work on ideas to improve the whole distribution as well as the |
| 4 |
> developer experience for everyone. I agree with others, who have |
| 5 |
> already mentioned that the Council should not just come up with ideas |
| 6 |
> and enforce them afterwards. Instead, the ideas should be discussed |
| 7 |
> publicly. Because after all, everything the Council does should serve |
| 8 |
> the distribution and the community. So in sum, I imagine the Council |
| 9 |
> to help to identify currently existing problems, look for possible |
| 10 |
> solutions and afterwards discuss them with the community. |
| 11 |
|
| 12 |
I agree with this, anything the council does should be discussed |
| 13 |
publically before action is taken. Someone else said that agenda items |
| 14 |
should be discussed on -project before the meeting and voted on during |
| 15 |
the meeting. I tend to agree with this. |
| 16 |
|
| 17 |
> Apart from that, I also see the opportunity for the Council to promote |
| 18 |
> Gentoo at different events to get recruits and help understaffed |
| 19 |
> projects as Brian also already mentioned. |
| 20 |
|
| 21 |
This is not specifically a council function; I see it as more a pr team |
| 22 |
function. I am open to helping with it as a council member, but I'm not |
| 23 |
quite sure what the council can do. |
| 24 |
|
| 25 |
> Before I continue to concretize this thought, a few words about my |
| 26 |
> work for Gentoo, for everyone who does not know me: I have mainly been |
| 27 |
> working on developer services and the infrastructure within Gentoo so |
| 28 |
> far. For instance, I'm one of the persons to blame for problems with |
| 29 |
> packages.g.o, planet.g.o, mirrorstats.g.o, the new archivestest.g.o or |
| 30 |
> the like. Apart from that, I'm working on the second version of the |
| 31 |
> Tyrian theme to unify our outer appearance, and I'm doing some further |
| 32 |
> internal infrastructure work. Finally, I am also still working towards |
| 33 |
> a unified code and automation platform like Gitlab or Gitea (in |
| 34 |
> combination with another automation platform). |
| 35 |
|
| 36 |
I'm on board with some kind of platform like this. |
| 37 |
I have experience administering gitlab, so I could assist with it if we |
| 38 |
go that route. I've also offered some updates to the gitea package, so I |
| 39 |
have been becoming familiar with it lately as well. |
| 40 |
|
| 41 |
> So how do I concretely imagine my work for the Council? Should I be |
| 42 |
> elected, my idea for the Council is to identify and document the |
| 43 |
> status quo first. That is, what are we already doing well and what |
| 44 |
> might be currently existing problems. Afterwards, I would like to help |
| 45 |
> to find possible solutions for the existing problems and discuss them |
| 46 |
> publicly. |
| 47 |
> One concrete project I would especially like to move forward is the |
| 48 |
> unified code and automation platform I've already mentioned above. |
| 49 |
|
| 50 |
I am interested in this project as well. We need to keep in mind that |
| 51 |
the platform we use needs to support multiple user interfaces; for |
| 52 |
example it should not force you to use the web to interact with it. |
| 53 |
Along this line, we should re-visit the wiki for the same reason. |
| 54 |
|
| 55 |
William |
Archives