Election: Better explain roles of Council

[Dhanesh B. Sabane]

Greetings everyone!

CommOps recently took up the task of improving the election process[1].  With respect to that and based on the conversations which took place in FLOCK 2016, we believe that bringing more exposure to the Council's roles and responsibilities will hopefully encourage more nominations and candidates in elections[2].

One way we can accomplish this is by updating the wiki[3] to provide more comprehensive information about the *roles*, *responsibilities*, *benefits* and *skills needed* to be a Council member.

A request to all the members to provide feedback on how this can be better handled to benefit the upcoming elections.

[1] https://pagure.io/fedora-commops/issue/90
[2] https://pagure.io/fedora-commops/issue/93
[3] https://fedoraproject.org/wiki/Council#Responsibilities

Regards, 
Dhanesh B. Sabane [dhanesh95]

[Brian Exelbierd]

Hi Danesh,

I think you have raised a good point, however I believe we should
approach this from a different angle.  In general, we want people to be
very familiar with the project before standing for a role on the
council.  I presume that anyone having an interest in running will not
only appreciate the role the council plays but also have attended many
council meetings to see how it functions.

Instead, I'd like to redirect your energy toward explaining the council
itself.  Like many partso fo Fedora, there is more that should be
written about the what, why, and how.  This would help new people
acclimate to the project and provide more transparency.  For the
non-elected roles we should flesh out the descriptions and
responsibilities as a part of this process.

Once that is complete we can decide if we actually need to further
explain the elected roles or not.

What do you think?

regards,

bex

On Wed, Nov 30, 2016, at 10:36 AM, Dhanesh B. Sabane wrote:
> Greetings everyone!
>
> CommOps recently took up the task of improving the election process[1]. 
> With respect to that and based on the conversations which took place in
> FLOCK 2016, we believe that bringing more exposure to the Council's roles
> and responsibilities will hopefully encourage more nominations and
> candidates in elections[2].
>
> One way we can accomplish this is by updating the wiki[3] to provide more
> comprehensive information about the *roles*, *responsibilities*,
> *benefits* and *skills needed* to be a Council member.
>
> A request to all the members to provide feedback on how this can be
> better handled to benefit the upcoming elections.
>
> [1] https://pagure.io/fedora-commops/issue/90
> [2] https://pagure.io/fedora-commops/issue/93
> [3] https://fedoraproject.org/wiki/Council#Responsibilities
>
> Regards, 
> Dhanesh B. Sabane [dhanesh95]
> _______________________________________________
> council-discuss mailing list -- [e-mail]
> To unsubscribe send an email to
> [e-mail]

[Dhanesh B. Sabane]

> Instead, I'd like to redirect your energy toward explaining the council
> itself.  Like many partso fo Fedora, there is more that should be
> written about the what, why, and how.  This would help new people
> acclimate to the project and provide more transparency.  For the
> non-elected roles we should flesh out the descriptions and
> responsibilities as a part of this process.
>
> Once that is complete we can decide if we actually need to further
> explain the elected roles or not.
>
> What do you think?

Hi Brian,
I think those are two very important points and we can surely divert our resources to tackle them.  I'll raise this issue in today's CommOps meeting and let's see how we can get things done.

Mr. Miller's suggestion will also be considered and I  will get back to this thread once we have a solid strategy.

Thanks a lot for your valuable feedback.

Regards, 
Dhanesh B. Sabane [dhanesh95]

[Matthew Miller]

On Wed, Nov 30, 2016 at 09:36:01AM -0000, Dhanesh B. Sabane wrote:
> One way we can accomplish this is by updating the wiki[3] to provide
> more comprehensive information about the *roles*, *responsibilities*,
> *benefits* and *skills needed* to be a Council member.

I don't think this is a bad idea, but I think that the council wiki page
is long enough already (and it went through a lot of back and forth).
If there's a need to expand more, let's link to a "for more info..."
page.

[Dhanesh B. Sabane]

Greetings Council!

In the recently concluded CommOps meeting[1], we had an intensive discussion session on this issue[2].  Brian made us realize that we are on a tight schedule and it would be extremely difficult to have any significant influence.  However, we still believe it is important to focus on improving communication of Council positions.  The purpose isn't to "lower the bar" for someone running for the Council, but rather, we want to improve the visibility and transparency of the work they do, so that more capable individuals feel confident enough to run and/or nominate others for these positions.  Thusly, we are proposing for a *FAQ* wiki page to have in place for Summer 2017 elections.  This may definitely help someone, who is interested but maybe not be fully engaged with the Council, to be able to understand some of the core responsibilities, and then nominate someone they believe is capable.

In the interest of time, we also decided to post a CommBlog article which, hopefully, will be helpful for the upcoming elections.[3]

Eager to know the Council's thoughts on the above mentioned points.

[1] https://meetbot.fedoraproject.org/fedora-meeting/2016-12-06/commops.2016-12-...
[2] https://pagure.io/fedora-commops/issue/93
[3] https://communityblog.fedoraproject.org/elections-2016-nominate-leadership/

Regards,
Dhanesh B. Sabane [dhanesh95]