Mid-Late Jan or so. We haven’t scheduled the budget meeting yet.
M
*From: *Steve Lime <[email protected]>
*Date: *Thursday, January 4, 2024 at 5:46 PM
*To: *Seth G <[email protected]>
*Cc: *Even Rouault <[email protected]>, Michael Smith
<[email protected]>, MapServer Devs
<[email protected]>
*Subject: *Re: [MapServer-dev] 2024 budget planning
Anyone know that deadline?
On Fri, Dec 29, 2023 at 10:05 AM Steve Lime <[email protected]
<mailto:[email protected]>> wrote:
I don't have any additions.
On Thu, Dec 28, 2023 at 3:48 AM Seth G <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
It seems many projects have submitted their budget requests
for next year to OSGeo - I presume there is an end-of-year
deadline to be met?
I've added in items from this thread to
https://github.com/MapServer/MapServer/wiki/MapServer-2024-Budget
<https://github.com/MapServer/MapServer/wiki/MapServer-2024-Budget>
Jeff has discussed the 8.2 release for January, so I've added
in the release manager role. I guess the requested amount
depends upon if there are also plans for additional patch
releases in 2024 and MapCache releases.
Once this value is finalised it would be good to take a vote
and submit to OSGeo in the next few days. Alternatively we can
just go with the 2021 value and vote now. If there are any
other items to add please edit the page.
I'll also look at creating a page of other ideas for MapServer
for sponsorship opportunities, similar to the GeoTools one at
https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities
<https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities>
Seth
--
web:https://geographika.net <https://geographika.net> &
https://mapserverstudio.net <https://mapserverstudio.net>
twitter: @geographika
On Thu, Dec 14, 2023, at 4:36 PM, Even Rouault wrote:
Hi,
I agree we should cut use of Travis if the budget for
MapServer is so low. Yes, the specificity of the Travis CI
checks is to test 2 versions of PHP, but I suspect this
could be migrated to GHA if needed (e.g perhaps using
https://github.com/setup-php/setup-php
<https://github.com/setup-php/setup-php>). For
AddressSanitizer, this would be trivial to port to GHA.
(GDAL only use of Travis CI is to test exotic
architectures, in particular ARM64, which aren't available
on GHA. But GDAL only uses the OSGeo provided budget for
that, so that's OK for it)
Even
Le 14/12/2023 à 16:18, Seth G a écrit :
It seems a shame to spend over 80% of the budget on
Travis, completely switching to GitHub Actions would
be another item it would be good to add to the
MapServer 2024 plan/budget and PSC vote.
There were some previous discussions about this in
2020 [1]. Since then GHA seems to have advanced whilst
Travis has stagnated. In addition MapCache switched
away from Travis [2]. I see GDAL still uses Travis so
maybe there are some advantages I'm not aware of.
As far as I can tell it is only the AddressSanitizer
run and PHP builds that Travis includes that aren't
already in GHA [2].
Seth
[1]
https://lists.osgeo.org/pipermail/mapserver-dev/2020-November/016302.html
<https://lists.osgeo.org/pipermail/mapserver-dev/2020-November/016302.html>
[2] https://github.com/MapServer/mapcache/pull/274
<https://github.com/MapServer/mapcache/pull/274>
[3]
https://github.com/MapServer/MapServer/blob/main/.travis.yml
<https://github.com/MapServer/MapServer/blob/main/.travis.yml>
On Thu, Dec 14, 2023, at 2:59 PM, Michael Smith wrote:
For 2023, some of the funds were used for the
Travis subscription for mapserver which is $828/yr
(69/mo). So $172 would be available for the rest
of the year. The PayPal donation would carry over.
Project funds do not.
Mike
--
Michael Smith
OSGeo Treasurer
[email protected] <mailto:[email protected]>
*From: *Steve Lime <[email protected]>
<mailto:[email protected]>
*Date: *Thursday, December 14, 2023 at 8:31 AM
*To: *Michael Smith <[email protected]>
<mailto:[email protected]>
*Cc: *Even Rouault <[email protected]>
<mailto:[email protected]>, Seth G
<[email protected]>
<mailto:[email protected]>, MapServer Devs
<[email protected]>
<mailto:[email protected]>
*Subject: *Re: [MapServer-dev] 2024 budget planning
Is there any chance of accessing the FY23 $'s?
Problem is that we don't have a project bank account.
There was also a $1,310 donation via PayPal in
March 2022 that looks to have come in via OSGeo
via PayPal but was earmarked specifically for
MapServer. Mike, I can send you a copy of that
email if you'd like.
--Steve
On Wed, Dec 13, 2023 at 4:34 PM Michael Smith
<[email protected]
<mailto:[email protected]>> wrote:
Proposed default for FY24 per project is $1000
USD. Yes you can request more than that but
there should be a plan for the additional
amounts voted by PSC.
Funds from donation are 295.45 (looks like it
was mostly in 2021 and a bit in 2022).
Mike
-
Michael Smith
OSGeo Treasurer
*From: *Steve Lime <[email protected]
<mailto:[email protected]>>
*Date: *Wednesday, December 13, 2023 at 4:56 PM
*To: *Even Rouault <[email protected]
<mailto:[email protected]>>, Michael
Smith <[email protected]
<mailto:[email protected]>>
*Cc: *Seth G <[email protected]
<mailto:[email protected]>>, MapServer
Devs <[email protected]
<mailto:[email protected]>>
*Subject: *Re: [MapServer-dev] 2024 budget
planning
Great ideas, I'd support both of them. The
question becomes how much to allocate in each
instance. I guess some basic questions I'd
have (and maybe Mike knows) are:
1. What's that standard per project budget
allocation from OSGeo? I thought it was
something like $1,500 but I'm not sure.
2. Is there any chance of getting $'s beyond
that? The 2020 budget referenced earlier
in the thread was submitted to the board
but it was pretty clear there was no
opportunity to secure funding beyond that
base amount.
3. We have some $'s that have been donated
via Paypal. I don't know the amount but
there should be at least $1,000 available
and that could be considered as another
means of paying for this work. Again, Mike
do you know what the MapServer balance is
via the donate button?
4. We are still in 2023 - can we allocate
this years' standard budget allocation to
this work or otherwise roll it over? I'd
like to know what our options are. We've
not done a good job of taking advantage of
the OSGeo funds available, even if they
are somewhat limited.
Seth, what level of support do you think you'd
need?
--Steve
On Thu, Dec 7, 2023 at 5:48 PM Even Rouault
via MapServer-dev
<[email protected]
<mailto:[email protected]>> wrote:
Hi Seth,
thanks for putting that together. The 2
topics (workshop and CITE tests)
look like excellent topics to be budgeted.
Even
Le 07/12/2023 à 11:02, Seth G via
MapServer-dev a écrit :
> Hi all,
>
> I've created a draft page for the budget
at
https://github.com/MapServer/MapServer/wiki/MapServer-2024-Budget
<https://github.com/MapServer/MapServer/wiki/MapServer-2024-Budget>
>
> I've also created two wiki pages for two
items I'd like to work on next year, and
to request some funds to help set aside
time to work on them. Both were discussed
with other members of the PSC at the
recent OSGeo Community Sprint:
>
> A new MapServer Workshop, see details at
https://github.com/MapServer/MapServer/wiki/MapServer-Workshop-2024
<https://github.com/MapServer/MapServer/wiki/MapServer-Workshop-2024>
> This would target FOSS4G Europe next
year. The deadline for submission is
January 14th 2024 so it would be good to
sort out a budget as soon as possible to
be able to submit. Workshops are 4 hours
in length.
>
> Automating and refreshing the MapServer
OGC CITE tests - see
https://github.com/MapServer/MapServer/wiki/MapServer-OGC-CITE-Tests
<https://github.com/MapServer/MapServer/wiki/MapServer-OGC-CITE-Tests>
>
> Let me know your thoughts on the above,
>
> Seth
> --
> web:https://geographika.net
<https://geographika.net> &
https://mapserverstudio.net
<https://mapserverstudio.net>
> twitter: @geographika
>
> On Thu, Nov 2, 2023, at 6:58 PM, Seth G
wrote:
>> Hi all,
>>
>> A wiki page sounds a good start.
Increased test coverage and OGC Maps
>> support would be two items I'd like to
propose.
>> We could also maybe use a GitHub
Discussions poll to allow users to
>> vote on some open issues to look at fixing?
>>
>> I think any unused funds for the year
remain with OSGeo and can't be
>> used for future years. Is it an option
to get a 2023 budget approved to
>> avoid losing these funds for this year?
>> There is the OSGeo Codesprint in Vienna
next week, and 5 of the PSC
>> members will be there so we could
arrange a PSC meeting and sign things
>> off quite quickly.
>>
>> Seth
>>
>> --
>> web:https://geographika.net
<https://geographika.net> &
https://mapserverstudio.net
<https://mapserverstudio.net>
>> twitter: @geographika
>>
>> On Wed, Nov 1, 2023, at 10:44 PM, Lime,
Steve D (MNIT) via MapServer-dev wrote:
>>> This is a good idea and something that
we haven't done in some time.
>>> There was a 2020 budget outline
>>>
(https://github.com/MapServer/MapServer/wiki/OSGeo-2020-Budget
<https://github.com/MapServer/MapServer/wiki/OSGeo-2020-Budget>) that
>>> was put together as an ask from the
board. If I recall correctly, they
>>> basically only allocated the normal
per project amount to the project.
>>> That's funding we've not taken
explicit advantage of most years
>>> although I don't know what happens to
those $'s if they go unclaimed.
>>> There is also a donation balance that
could/should be tapped to fund
>>> activities.
>>>
>>> --Steve
>>>
>>> -----Original Message-----
>>> From: MapServer-dev
<[email protected]
<mailto:[email protected]>> On
Behalf
>>> Of Jeff McKenna via MapServer-dev
>>> Sent: Wednesday, November 1, 2023 1:00 PM
>>> To: 'MapServer Dev Mailing List'
<[email protected]
<mailto:[email protected]>>
>>> Subject: [MapServer-dev] 2024 budget
planning
>>>
>>> Hi MapServer community (devs, users,
packagers, promoters, all),
>>>
>>> I see other projects beginning early
discussions on planning for 2024
>>> budget spending. I would like to
start a wiki page for the 2024 budget
>>> for MapServer. I am planning on
including those items
>>>
never-funded-yet-heavily-relied-upon-by-users such
as releases,
>>> packaging, testing/CI infrastructure
maintenance, and documentation, as
>>> well as source code contributions (in
other words, including the full
>>> dev community of MapServer in the budget).
>>>
>>> I think 2024 is a good time to create
a realistic budget for MapServer,
>>> and then share that publicly with the
FOSS4G community. I think we'd
>>> be happily surprised that
organizations are willing to support the
>>> sustainability of MapServer.
Worst-case scenario is that we have a
>>> publicly available realistic view of
the cost of keeping MapServer
>>> reliable, secure, and fast, that we
can expand upon in future years.
>>>
>>> Happy to read other thoughts here,
from everyone passionate about MapServer.
>>>
>>> thanks!
>>>
>>> -jeff
>>>
>>> --
>>> Jeff McKenna
>>> GatewayGeo: Developers of MS4W, &
offering MapServer Consulting/Dev
>>> co-founder of FOSS4G
>>>
>>>
_______________________________________________
>>> MapServer-dev mailing list
>>> [email protected]
<mailto:[email protected]>
>>>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
<https://lists.osgeo.org/mailman/listinfo/mapserver-dev>
>
_______________________________________________
> MapServer-dev mailing list
> [email protected]
<mailto:[email protected]>
>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
<https://lists.osgeo.org/mailman/listinfo/mapserver-dev>
--
http://www.spatialys.com
<http://www.spatialys.com>
My software is free, but my time generally
not.
_______________________________________________
MapServer-dev mailing list
[email protected]
<mailto:[email protected]>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
<https://lists.osgeo.org/mailman/listinfo/mapserver-dev>
--
http://www.spatialys.com <http://www.spatialys.com>
My software is free, but my time generally not.
