Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Jean-Paul Calderone]

On Sun, Jan 3, 2021 at 10:00 PM Ian Haywood  wrote:

> I think having a project coordinator as   a *first* priority isn't a good
> idea (not saying it isn't down the track)
>
> Currently there's little to coordinate as the core team aren't active in
> planning or review. can the team be expanded ? (I'm not angling for a role
> myself)
>

Since Glyph has asked that this discussion move to a different forum, I
won't respond to this counter-proposal here.

Jean-Paul


> Ian
> On 4/01/2021 11:59 am, Adi Roiban wrote:
>
>
>
> On Mon, 4 Jan 2021 at 00:54, Glyph  wrote:
>
>> It’s complicated and I’m not a lawyer, so maybe it is indeed not a
>> problem. But in brief it’s like trademark protection, kind of, in that it
>> becomes SFC’s problem to be aware that you’ve said these things and tell
>> you not to say them. The twisted project (which is a bit of an amorphous
>> concept to begin with) has authorized SFC to be its fiscal sponsor, the SFC
>> has gone through  the rigamarole with the IRS to ensure this is an
>> exempt-able public benefit activity, and now someone is making claims about
>> the project hiring, which they’re on the hook for. How does the IRS know
>> your status of affiliation with the project or the conservancy for sure?
>> Somebody has to investigate it, investigating means asking a bunch of
>> questions and sucking up the SFC’s time and energy, even if no enforcement
>> action is ever formally taken.
>>
>> In short: talk to the SFC first about the project’s status, get an actual
>> official recommendation and not my random opinion about what may or may not
>> be a problem, before doing anything related to fundraising. I can’t say
>> anything authoritative about what is allowed, because as far as I
>> understand it, *nothing* is allowed without untangling the PLC/approval
>> process first. :-)
>>
>> (Except to raise money for the already-authorized expenses related to the
>> continued hosting of twistedmatrix.com, of course.)
>>
>
> Thanks for the info and sorry for the trouble :)
>
> I will try to send a (private) message to SFC these days to untangle the
> PLC team and I will add you to CC.
>
> Until we solve the PLC issue, I would consider this discussion blocked.
>
> Cheers
> --
> Adi Roiban
>
> ___
> Twisted-Python mailing 
> listTwisted-Python@twistedmatrix.comhttps://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Ian Haywood]

I think having a project coordinator as   a *first* priority isn't a 
good idea (not saying it isn't down the track)


Currently there's little to coordinate as the core team aren't active in 
planning or review. can the team be expanded ? (I'm not angling for a 
role myself)


Ian

On 4/01/2021 11:59 am, Adi Roiban wrote:



On Mon, 4 Jan 2021 at 00:54, Glyph > wrote:


It’s complicated and I’m not a lawyer, so maybe it is indeed not a
problem. But in brief it’s like trademark protection, kind of, in
that it becomes SFC’s problem to be aware that you’ve said these
things and tell you not to say them. The twisted project (which is
a bit of an amorphous concept to begin with) has authorized SFC to
be its fiscal sponsor, the SFC has gone through  the rigamarole
with the IRS to ensure this is an exempt-able public benefit
activity, and now someone is making claims about the project
hiring, which they’re on the hook for. How does the IRS know your
status of affiliation with the project or the conservancy for
sure? Somebody has to investigate it, investigating means asking a
bunch of questions and sucking up the SFC’s time and energy, even
if no enforcement action is ever formally taken.

In short: talk to the SFC first about the project’s status, get an
actual official recommendation and not my random opinion about
what may or may not be a problem, before doing anything related to
fundraising. I can’t say anything authoritative about what is
allowed, because as far as I understand it, *nothing* is allowed
without untangling the PLC/approval process first. :-)

(Except to raise money for the already-authorized expenses related
to the continued hosting of twistedmatrix.com
, of course.)


Thanks for the info and sorry for the trouble :)

I will try to send a (private) message to SFC these days to untangle 
the PLC team and I will add you to CC.


Until we solve the PLC issue, I would consider this discussion blocked.

Cheers
--
Adi Roiban

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Adi Roiban]

On Mon, 4 Jan 2021 at 00:54, Glyph  wrote:

> It’s complicated and I’m not a lawyer, so maybe it is indeed not a
> problem. But in brief it’s like trademark protection, kind of, in that it
> becomes SFC’s problem to be aware that you’ve said these things and tell
> you not to say them. The twisted project (which is a bit of an amorphous
> concept to begin with) has authorized SFC to be its fiscal sponsor, the SFC
> has gone through  the rigamarole with the IRS to ensure this is an
> exempt-able public benefit activity, and now someone is making claims about
> the project hiring, which they’re on the hook for. How does the IRS know
> your status of affiliation with the project or the conservancy for sure?
> Somebody has to investigate it, investigating means asking a bunch of
> questions and sucking up the SFC’s time and energy, even if no enforcement
> action is ever formally taken.
>
> In short: talk to the SFC first about the project’s status, get an actual
> official recommendation and not my random opinion about what may or may not
> be a problem, before doing anything related to fundraising. I can’t say
> anything authoritative about what is allowed, because as far as I
> understand it, *nothing* is allowed without untangling the PLC/approval
> process first. :-)
>
> (Except to raise money for the already-authorized expenses related to the
> continued hosting of twistedmatrix.com, of course.)
>

Thanks for the info and sorry for the trouble :)

I will try to send a (private) message to SFC these days to untangle the
PLC team and I will add you to CC.

Until we solve the PLC issue, I would consider this discussion blocked.

Cheers
-- 
Adi Roiban
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Glyph]

It’s complicated and I’m not a lawyer, so maybe it is indeed not a problem. But 
in brief it’s like trademark protection, kind of, in that it becomes SFC’s 
problem to be aware that you’ve said these things and tell you not to say them. 
The twisted project (which is a bit of an amorphous concept to begin with) has 
authorized SFC to be its fiscal sponsor, the SFC has gone through the 
rigamarole with the IRS to ensure this is an exempt-able public benefit 
activity, and now someone is making claims about the project hiring, which 
they’re on the hook for. How does the IRS know your status of affiliation with 
the project or the conservancy for sure? Somebody has to investigate it, 
investigating means asking a bunch of questions and sucking up the SFC’s time 
and energy, even if no enforcement action is ever formally taken.  

In short: talk to the SFC first about the project’s status, get an actual 
official recommendation and not my random opinion about what may or may not be 
a problem, before doing anything related to fundraising. I can’t say anything 
authoritative about what is allowed, because as far as I understand it, 
*nothing* is allowed without untangling the PLC/approval process first. :-)  

(Except to raise money for the already-authorized expenses related to the 
continued hosting of twistedmatrix.com, of course.)  

-g

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Adi Roiban]

On Sun, 3 Jan 2021 at 23:36, Glyph  wrote:

> You can’t fundraise for a job opening that you haven’t cleared with the
> SFC as mission-aligned and properly transparent; this could get them in
> trouble with the IRS. You’ll need to clear this by writing a grant proposal
> and having it approved first. Please delete this posting from the sponsors
> page as soon as you can, since even posting to this list probably
> constitutes public advertising.
>

Hi,

I have remove the info.
The fundraising was never active. This was still WIP waiting for some
format approval.

I think that I have mentioned that I have no intention to apply for any of
these jobs and only volunteer to bootstrap this process.

I hope nobody will get into any trouble by my actions.

To me it makes no sense.
How can the IRS think that SFC is at fault for a public message posted by
me, someone with no affiliation to Twisted or SFC ?

Cheers


> On January 3, 2021 at 2:46:42 PM, Adi Roiban (a...@roiban.ro) wrote:
>
>>
>>
>> On Sun, 3 Jan 2021 at 20:30, Jean-Paul Calderone <
>> exar...@twistedmatrix.com> wrote:
>>
>>> On Wed, Dec 23, 2020 at 4:41 PM Adi Roiban  wrote:
>>>
 Hi,

 I started a separate discussion to confirm the goal for a future
 fundraising.

 Top priority - Pay someone to help with the review queue
 Nice to have - Move server/services to Azure VM -  We have at least
 $100 monthly allowance for Azure not sure if we still have the huge
 $2000 allowance on rackspace.
 Nice to have - Migrate Trac wiki to GitHub Wiki
 Nice to have - Migrate Trac Ticket to GitHub Issues

>>>
>>> I have a suggestion for another priority to be inserted above that top
>>> priority - pay someone to look after the day-to-day logistics of the
>>> project.  For example: to triage tickets in the issue tracker (identify
>>> duplicates to avoid redundant effort, classify issues by feature request vs
>>> defect vs regression, etc), keep track of the release process so releases
>>> are completed in a timely manner, identify and eliminate friction in the
>>> development process, and identify big-picture directions / priorities /
>>> roadmap items and track and coordinate efforts to achieve them.  I don't
>>> think someone could be hired to set the Twisted roadmap but someone could
>>> be hired to solicit this information from core developers and the wider
>>> community and organize it into a coherent plan.
>>>
>>>
>> Many thanks for your comments.
>> I agree.
>>
>> In this case, I think that for any near-future fundraising effort
>> (including GitHub Sponsors) we should have a single goal:
>>
>> 1. Raise money to hire a project manager.
>>
>> That will be a part time job and the person will work on other projects.
>>
>> The job activities will be (non exhaustive list - feel free to suggest):
>>
>> * triage tickets
>> * act as the release manager (the actual release has some automation) so
>> this is more about communication
>> * identify friction in the development process and document and try to
>> get consensus for a propose solution (the actual implementation can be done
>> by someone else)
>> * identify big-picture directions / priorities / roadmap items and track
>> and coordinate efforts to achieve them.
>> * help with fundraising / communication to future sponsors
>>
>> 
>>
>> Do you have any idea of the required effort for a project manager for
>> Twisted?
>> Maybe we can start with raising money to hire someone for 10 hours per
>> week.
>> Please suggest a different number of hours if you think that 10 hours are
>> not a good start.
>>
>> I think that at least for the first month, 10 hours per week is not
>> much...
>> but maybe after the second month, we can have 5 hours per week for
>> project management
>> and use extra money for the review queue or implement the top priority
>> tasks identified by the project manager.
>>
>> ---
>>
>> Then, if we raise more than 10 hours per week, we can dedicate that money
>> to code review.
>>
>> Then, if we ran out of reviews in the queue, use the leftover money for
>> reducing operation overhead / removing roadblock.
>>
>>
>>> Ideally this person could also look after fundraising efforts to ensure
>>> that there are funds to continue to support their other activities.
>>>
>>>
>> We have a catch-22 situation here ... we need to hire someone to work on
>> fundraising ... we need to raise funds to hire someone :)
>>
>> I can volunteer to bootstrap this effort and try to raise initial money
>> to find a project manager that can look after future fundraising.
>> I don't have much free time and I am not a good project manager or
>> communication manager :)
>>
>> Right now, I don't know who we could hire and what could be the selection
>> criteria ...
>>
>> But I think that we can focus to see if we can raise 10 hours per week
>> and then worry about finding the right person :)
>>
>> Helping with the review queue is great but it's a purely reactive

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Craig Rodrigues]

On Wed, Dec 23, 2020 at 1:41 PM Adi Roiban  wrote:

> Hi,
>
> I started a separate discussion to confirm the goal for a future
> fundraising.
>
> Top priority - Pay someone to help with the review queue
> Nice to have - Move server/services to Azure VM -  We have at least $100
> monthly allowance for Azure not sure if we still have the huge $2000
> allowance on rackspace.
> Nice to have - Migrate Trac wiki to GitHub Wiki
>
>
Adi,

I am glad that you are enthusiastic about the Twisted project,
but I just want to raise my voice that I disagree with most of what you
recommend as future actions.

I am skeptical about your recommendation when it comes to accepting
donations, spending
money, and hiring people, etc.   If these things are necessary, I would
like to see this as part of
a fully fleshed out plan that is approved by a proper governance structure.

Personally, I'm not convinced that getting more monetary donations and
hiring people will improve the Twisted project.  I could be wrong about
this,
but I need to be convinced.

In this thread:
https://twistedmatrix.com/pipermail/twisted-python/2020-December/065341.html
you raised some valid points about the project leadership committee.  I
would like to see the points in that
thread discussed to completion.
For starters, the people on the existing project leadership committee
should be given the chance
to respond, and hand the baton to the next project leadership committee.

The fact that details of the project committee are not written down in a
place which is available to the public
seems like something that we can fix, without involving discussions about
spending money and hiring people.

Once there is a proper governance structure in place for the Twisted
project,
I think that any discussions about spending money and hiring can be
discussed more easily.

--
Craig
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Glyph]

(It might be generally good to stop discussing these priorities on a public 
list, and instead make a private list that anyone can request to join, but e.g. 
having joined precludes or disqualifies one from bidding on any resulting 
funded efforts. The big thing to avoid here is self dealing, ie having a clown 
showing up and advocating really aggressively that the thing Twisted really 
needs is a bunch of balloon animals that conveniently only they know how to 
make. Having a private group with documented members for discussion provides a 
nice audit trail that this isn’t happening.)

On January 3, 2021 at 3:32:56 PM, Glyph 
(gl...@twistedmatrix.com(mailto:gl...@twistedmatrix.com)) wrote:

> You can’t fundraise for a job opening that you haven’t cleared with the SFC 
> as mission-aligned and properly transparent; this could get them in trouble 
> with the IRS. You’ll need to clear this by writing a grant proposal and 
> having it approved first. Please delete this posting from the sponsors page 
> as soon as you can, since even posting to this list probably constitutes 
> public advertising.
>  
> On January 3, 2021 at 2:46:42 PM, Adi Roiban 
> (a...@roiban.ro(mailto:a...@roiban.ro)) wrote:
>  
> >  
> >  
> > On Sun, 3 Jan 2021 at 20:30, Jean-Paul Calderone 
> > mailto:exar...@twistedmatrix.com)> wrote:
> > > On Wed, Dec 23, 2020 at 4:41 PM Adi Roiban 
> > > mailto:a...@roiban.ro)> wrote:
> > > > Hi,  
> > > >  
> > > > I started a separate discussion to confirm the goal for a future 
> > > > fundraising.  
> > > >  
> > > > Top priority - Pay someone to help with the review queue  
> > > > Nice to have - Move server/services to Azure VM - We have at least $100 
> > > > monthly allowance for Azure not sure if we still have the huge 
> > > > $2000 allowance on rackspace.
> > > > Nice to have - Migrate Trac wiki to GitHub Wiki
> > > > Nice to have - Migrate Trac Ticket to GitHub Issues
> > >  
> > > I have a suggestion for another priority to be inserted above that top 
> > > priority - pay someone to look after the day-to-day logistics of the 
> > > project. For example: to triage tickets in the issue tracker (identify 
> > > duplicates to avoid redundant effort, classify issues by feature request 
> > > vs defect vs regression, etc), keep track of the release process so 
> > > releases are completed in a timely manner, identify and eliminate 
> > > friction in the development process, and identify big-picture directions 
> > > / priorities / roadmap items and track and coordinate efforts to achieve 
> > > them. I don't think someone could be hired to set the Twisted roadmap but 
> > > someone could be hired to solicit this information from core developers 
> > > and the wider community and organize it into a coherent plan.  
> > >  
> >  
> > Many thanks for your comments.  
> > I agree.
> >  
> > In this case, I think that for any near-future fundraising effort 
> > (including GitHub Sponsors) we should have a single goal:  
> >  
> > 1. Raise money to hire a project manager.  
> >  
> > That will be a part time job and the person will work on other projects.
> >  
> > The job activities will be (non exhaustive list - feel free to suggest):  
> >  
> > * triage tickets
> > * act as the release manager (the actual release has some automation) so 
> > this is more about communication
> > * identify friction in the development process and document and try to get 
> > consensus for a propose solution (the actual implementation can be done by 
> > someone else)
> > * identify big-picture directions / priorities / roadmap items and track 
> > and coordinate efforts to achieve them.
> > * help with fundraising / communication to future sponsors  
> >  
> > 
> >  
> > Do you have any idea of the required effort for a project manager for 
> > Twisted?
> > Maybe we can start with raising money to hire someone for 10 hours per 
> > week.  
> > Please suggest a different number of hours if you think that 10 hours are 
> > not a good start.
> >  
> > I think that at least for the first month, 10 hours per week is not much... 
> >  
> > but maybe after the second month, we can have 5 hours per week for project 
> > management
> > and use extra money for the review queue or implement the top priority 
> > tasks identified by the project manager.
> >  
> > ---
> >  
> > Then, if we raise more than 10 hours per week, we can dedicate that money 
> > to code review.  
> >  
> > Then, if we ran out of reviews in the queue, use the leftover money for 
> > reducing operation overhead / removing roadblock.
> >  
> > > Ideally this person could also look after fundraising efforts to ensure 
> > > that there are funds to continue to support their other activities.
> > >  
> >  
> > We have a catch-22 situation here ... we need to hire someone to work on 
> > fundraising ... we need to raise funds to hire someone :)
> >  
> > I can volunteer to bootstrap this effort and try to raise initial money to 
> > 

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Glyph]

You can’t fundraise for a job opening that you haven’t cleared with the SFC as 
mission-aligned and properly transparent; this could get them in trouble with 
the IRS. You’ll need to clear this by writing a grant proposal and having it 
approved first. Please delete this posting from the sponsors page as soon as 
you can, since even posting to this list probably constitutes public 
advertising.

On January 3, 2021 at 2:46:42 PM, Adi Roiban 
(a...@roiban.ro(mailto:a...@roiban.ro)) wrote:

>  
>  
> On Sun, 3 Jan 2021 at 20:30, Jean-Paul Calderone 
> mailto:exar...@twistedmatrix.com)> wrote:
> > On Wed, Dec 23, 2020 at 4:41 PM Adi Roiban 
> > mailto:a...@roiban.ro)> wrote:
> > > Hi,  
> > >  
> > > I started a separate discussion to confirm the goal for a future 
> > > fundraising.  
> > >  
> > > Top priority - Pay someone to help with the review queue  
> > > Nice to have - Move server/services to Azure VM - We have at least $100 
> > > monthly allowance for Azure not sure if we still have the huge $2000 
> > > allowance on rackspace.
> > > Nice to have - Migrate Trac wiki to GitHub Wiki
> > > Nice to have - Migrate Trac Ticket to GitHub Issues
> >  
> > I have a suggestion for another priority to be inserted above that top 
> > priority - pay someone to look after the day-to-day logistics of the 
> > project. For example: to triage tickets in the issue tracker (identify 
> > duplicates to avoid redundant effort, classify issues by feature request vs 
> > defect vs regression, etc), keep track of the release process so releases 
> > are completed in a timely manner, identify and eliminate friction in the 
> > development process, and identify big-picture directions / priorities / 
> > roadmap items and track and coordinate efforts to achieve them. I don't 
> > think someone could be hired to set the Twisted roadmap but someone could 
> > be hired to solicit this information from core developers and the wider 
> > community and organize it into a coherent plan.  
> >  
>  
> Many thanks for your comments.  
> I agree.
>  
> In this case, I think that for any near-future fundraising effort (including 
> GitHub Sponsors) we should have a single goal:  
>  
> 1. Raise money to hire a project manager.  
>  
> That will be a part time job and the person will work on other projects.
>  
> The job activities will be (non exhaustive list - feel free to suggest):  
>  
> * triage tickets
> * act as the release manager (the actual release has some automation) so this 
> is more about communication
> * identify friction in the development process and document and try to get 
> consensus for a propose solution (the actual implementation can be done by 
> someone else)
> * identify big-picture directions / priorities / roadmap items and track and 
> coordinate efforts to achieve them.
> * help with fundraising / communication to future sponsors  
>  
> 
>  
> Do you have any idea of the required effort for a project manager for Twisted?
> Maybe we can start with raising money to hire someone for 10 hours per week.  
> Please suggest a different number of hours if you think that 10 hours are not 
> a good start.
>  
> I think that at least for the first month, 10 hours per week is not much...  
> but maybe after the second month, we can have 5 hours per week for project 
> management
> and use extra money for the review queue or implement the top priority tasks 
> identified by the project manager.
>  
> ---
>  
> Then, if we raise more than 10 hours per week, we can dedicate that money to 
> code review.  
>  
> Then, if we ran out of reviews in the queue, use the leftover money for 
> reducing operation overhead / removing roadblock.
>  
> > Ideally this person could also look after fundraising efforts to ensure 
> > that there are funds to continue to support their other activities.
> >  
>  
> We have a catch-22 situation here ... we need to hire someone to work on 
> fundraising ... we need to raise funds to hire someone :)
>  
> I can volunteer to bootstrap this effort and try to raise initial money to 
> find a project manager that can look after future fundraising.
> I don't have much free time and I am not a good project manager or 
> communication manager :)
>  
> Right now, I don't know who we could hire and what could be the selection 
> criteria ...
>  
> But I think that we can focus to see if we can raise 10 hours per week and 
> then worry about finding the right person :)  
>  
> > Helping with the review queue is great but it's a purely reactive activity. 
> > This is fine so far as it goes but it leaves the project without a coherent 
> > direction, which in turn makes less productive use of the resources 
> > available. The project should continue to operate reactively to address 
> > issues raised by the community but to really stay relevant, the core 
> > Twisted team itself also needs to identify coherent future goals and work 
> > to achieve them.  
> >  
> > Messing with 

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Adi Roiban]

On Sun, 3 Jan 2021 at 20:30, Jean-Paul Calderone 
wrote:

> On Wed, Dec 23, 2020 at 4:41 PM Adi Roiban  wrote:
>
>> Hi,
>>
>> I started a separate discussion to confirm the goal for a future
>> fundraising.
>>
>> Top priority - Pay someone to help with the review queue
>> Nice to have - Move server/services to Azure VM -  We have at least $100
>> monthly allowance for Azure not sure if we still have the huge $2000
>> allowance on rackspace.
>> Nice to have - Migrate Trac wiki to GitHub Wiki
>> Nice to have - Migrate Trac Ticket to GitHub Issues
>>
>
> I have a suggestion for another priority to be inserted above that top
> priority - pay someone to look after the day-to-day logistics of the
> project.  For example: to triage tickets in the issue tracker (identify
> duplicates to avoid redundant effort, classify issues by feature request vs
> defect vs regression, etc), keep track of the release process so releases
> are completed in a timely manner, identify and eliminate friction in the
> development process, and identify big-picture directions / priorities /
> roadmap items and track and coordinate efforts to achieve them.  I don't
> think someone could be hired to set the Twisted roadmap but someone could
> be hired to solicit this information from core developers and the wider
> community and organize it into a coherent plan.
>
>
Many thanks for your comments.
I agree.

In this case, I think that for any near-future fundraising effort
(including GitHub Sponsors) we should have a single goal:

1. Raise money to hire a project manager.

That will be a part time job and the person will work on other projects.

The job activities will be (non exhaustive list - feel free to suggest):

* triage tickets
* act as the release manager (the actual release has some automation) so
this is more about communication
* identify friction in the development process and document and try to get
consensus for a propose solution (the actual implementation can be done by
someone else)
* identify big-picture directions / priorities / roadmap items and track
and coordinate efforts to achieve them.
* help with fundraising / communication to future sponsors



Do you have any idea of the required effort for a project manager for
Twisted?
Maybe we can start with raising money to hire someone for 10 hours per week.
Please suggest a different number of hours if you think that 10 hours are
not a good start.

I think that at least for the first month, 10 hours per week is not much...
but maybe after the second month, we can have 5 hours per week for project
management
and use extra money for the review queue or implement the top priority
tasks identified by the project manager.

---

Then, if we raise more than 10 hours per week, we can dedicate that money
to code review.

Then, if we ran out of reviews in the queue, use the leftover money for
reducing operation overhead / removing roadblock.


> Ideally this person could also look after fundraising efforts to ensure
> that there are funds to continue to support their other activities.
>
>
We have a catch-22 situation here ... we need to hire someone to work on
fundraising ... we need to raise funds to hire someone :)

I can volunteer to bootstrap this effort and try to raise initial money to
find a project manager that can look after future fundraising.
I don't have much free time and I am not a good project manager or
communication manager :)

Right now, I don't know who we could hire and what could be the selection
criteria ...

But I think that we can focus to see if we can raise 10 hours per week and
then worry about finding the right person :)

Helping with the review queue is great but it's a purely reactive
> activity.  This is fine so far as it goes but it leaves the project without
> a coherent direction, which in turn makes less productive use of the
> resources available.  The project should continue to operate reactively to
> address issues raised by the community but to really stay relevant, the
> core Twisted team itself also needs to identify coherent future goals and
> work to achieve them.
>
> Messing with CI configuration, wikis, issue tracking, etc, may also all be
> beneficial but they're not useful goals in themselves - they should all be
> in support of a goal like reducing operational overhead to allow resources
> to be directed elsewhere or removing roadblocks that stand in the way of
> other contributors having an impact.
> 
>

True.

See the updated GitHub Sponsor page

https://github.com/sponsors/twisted?preview=true

Let me know what you think and if you think that is ready to make it public.

We need feedback on everything on the preview page:

* Project goal
* Support tiers
* Project description

Cheers
-- 
Adi Roiban
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com

Re: [Twisted-Python] Plan/Goal for GitHub Sponsors

[Jean-Paul Calderone]

On Wed, Dec 23, 2020 at 4:41 PM Adi Roiban  wrote:

> Hi,
>
> I started a separate discussion to confirm the goal for a future
> fundraising.
>
> Top priority - Pay someone to help with the review queue
> Nice to have - Move server/services to Azure VM -  We have at least $100
> monthly allowance for Azure not sure if we still have the huge $2000
> allowance on rackspace.
> Nice to have - Migrate Trac wiki to GitHub Wiki
> Nice to have - Migrate Trac Ticket to GitHub Issues
>

I have a suggestion for another priority to be inserted above that top
priority - pay someone to look after the day-to-day logistics of the
project.  For example: to triage tickets in the issue tracker (identify
duplicates to avoid redundant effort, classify issues by feature request vs
defect vs regression, etc), keep track of the release process so releases
are completed in a timely manner, identify and eliminate friction in the
development process, and identify big-picture directions / priorities /
roadmap items and track and coordinate efforts to achieve them.  I don't
think someone could be hired to set the Twisted roadmap but someone could
be hired to solicit this information from core developers and the wider
community and organize it into a coherent plan.

Ideally this person could also look after fundraising efforts to ensure
that there are funds to continue to support their other activities.

Helping with the review queue is great but it's a purely reactive
activity.  This is fine so far as it goes but it leaves the project without
a coherent direction, which in turn makes less productive use of the
resources available.  The project should continue to operate reactively to
address issues raised by the community but to really stay relevant, the
core Twisted team itself also needs to identify coherent future goals and
work to achieve them.

Messing with CI configuration, wikis, issue tracking, etc, may also all be
beneficial but they're not useful goals in themselves - they should all be
in support of a goal like reducing operational overhead to allow resources
to be directed elsewhere or removing roadblocks that stand in the way of
other contributors having an impact.

Jean-Paul


>
> That is all..but first we should solve the release queue.
> Cheers
> --
> Adi Roiban
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Plan/Goal for GitHub Sponsors

[Adi Roiban]

Hi,

I started a separate discussion to confirm the goal for a future
fundraising.

Top priority - Pay someone to help with the review queue
Nice to have - Move server/services to Azure VM -  We have at least $100
monthly allowance for Azure not sure if we still have the huge $2000
allowance on rackspace.
Nice to have - Migrate Trac wiki to GitHub Wiki
Nice to have - Migrate Trac Ticket to GitHub Issues

That is all..but first we should solve the release queue.
Cheers
-- 
Adi Roiban
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python