[Qgis-psc] Python API documentation part 3, Spreadshirt

[Andreas Neumann]

Hi,

Richard - I agree that it is not so nice, not knowing in advance how much
funds such a work package really requires. I would also prefer that things
stay within budget - but as Denis said, it is often hard to know how much
work is involved in advance. Also he said, that we worked many more hours
that he invoiced so far. Personally, I would prefer finishing projects
(such as the Python API documentation), rather then letting them rotten at
2/3 or 3/4 finished and spend the funds on something else.

Thanks for your understanding,
Andreas


On 30 April 2018 at 06:49, Richard Duivenvoorde <rdmailings at duif.net> wrote:

> Hi Andreas,
>
> Ok for me, with the following remarks:
>
> - I'm very happy with the result
> - it is indeed an example of work to be done which is hard to be
> financed by 'users'
> - but think that this project takes a big part of the financing budget
> (in 3 steps), compared to other things on the todo list which are either
> done as volunteers (or not done)
> - and would prefer next time to do more real budgetting of projects
> alike: we should pay a fixed amount for a finished product, no slippery
> slopes
>
> Regards,
>
> Richard Duivenvoorde
>
> ps we also have 500 euro 'frozen' money at spreadshirt.COM (US shop),
> but we have to take a descision on if we are a not-for-profit or not
> (aka we need to do some tax-paper-work there...)
>
> On 27-04-18 15:29, Andreas Neumann wrote:
> > Dear PSC,
> >
> > Denis Rouzaud proposes a part 3 (final part) to complete the Python API
> > documentation - see
> > https://lists.osgeo.org/pipermail/qgis-psc/2018-April/006090.html -
> > Denis proposes six more days.
> >
> > The question has surfaced, whether this third part should be financed
> > through a QGIS grant proposal or through the regular budget where we
> > have set aside money for Python API documentation.
> >
> > The situation is that the proposed annual budget for Python API
> > documentation is already used up by parts 1 and 2 - but I would
> > nevertheless think that we should finance part 3 (the final part) the
> > Python API documentation outside of the QGIS grants - use the Python API
> > doc budgetary item and just overdraw that item. We started with a plus
> > of 63k into the new year and we can afford to overdraw the budget if
> > necessary. See also
> > https://www.qgis.org/en/_downloads/QGISBudget2018.pdf for the approved
> > budget.
> >
> > I think a good Python API documentation is very important for the
> > project, esp. at the current times where plugin authors will have a lot
> > of work porting their plugins to support QGIS 3.
> >
> > PSC members: can you please respond if you are ok with this proposal?
> >
> > -----------
> >
> > One other, positive, news: Spreadshirt already generated 370 € this year
> > - way more thant what we had in past years and already more than the 100
> > € I had in the budget. Also, we spent only half of the planned expenses
> > for the Madeira dev meeting - thanks to the local organizers/sponsors
> > and due to the fact that quite a few devs did not ask for reimbursements.
> >
> > Greetings,
> > Andreas
> >
> > --
> >
> > --
> > Andreas Neumann
> > QGIS.ORG <http://QGIS.ORG> board member (treasurer)
> >
> >
> > _______________________________________________
> > Qgis-psc mailing list
> > Qgis-psc at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/qgis-psc
> >
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc




-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20180430/ef19be12/attachment.html>