/logging/ it looks
like it should be possible to have Horizon's settings module disable
Django's logging configuration and call oslo.log to do that
configuration. I wonder if it would make sense to do that, for
consistency with the other services?
Doug
>
> [1] https://docs.djangoproject.c
Luka Peschke writes:
> Hello Doug,
>
> Here's the patch: https://review.openstack.org/#/c/616205/. If it is
> not merged by Friday (date of the first meeting), I'll send the log of
> the first meeting to this ML.
>
> Luka
I was mostly concerned with future meetings, so th
se propose an update to the openstack-infra/irc-meetings repository
to register the meeting info so it shows up on eavesdrop.openstack.org
and the calendar published there. That will make it easier for other
folks to find the meeting and keep it on their schedule.
--
Doug
___
Joshua Cornutt writes:
> On Wed, Nov 7, 2018 at 7:30 AM Doug Hellmann wrote:
>>
>> Joshua Cornutt writes:
>>
>> > Doug,
>> >
>> > I have such a list put together (my various installation documents for
>> > getting these clouds wo
Mohammed Naser writes:
> On Wed, Nov 7, 2018 at 2:07 PM Dr. Jens Harbott (frickler)
> wrote:
>>
>> 2018-11-07 12:47 GMT+00:00 Mohammed Naser :
>> > On Wed, Nov 7, 2018 at 1:37 PM Doug Hellmann wrote:
>> >>
>> >> Corey Bryant writes:
>>
to start. It lets us make incremental
progress while we take the time to think about the python version
management question more broadly. We can come back to the other projects
to add 3.7 jobs and remove 3.5 jobs when we have that plan worked out.
Doug
Joshua Cornutt writes:
> Doug,
>
> I have such a list put together (my various installation documents for
> getting these clouds working in FIPS mode) but it's hardly ready for
> public consumption. I planned on releasing each bit as a code change
> and/or bug ticket and let
th bionic.
>
> -gmann
I like the approach of updating the devstack jobs to move everything to
Bionic at one time because it sounds like it presents less risk of us
ending up with something that looks like it works together but doesn't
actually
Luke Hinds writes:
> On Tue, Nov 6, 2018 at 2:04 PM Julia Kreger
> wrote:
>
>>
>>
>> On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann
>> wrote:
>>
>>> Sean McGinnis writes:
>>>
>>> > I'm interested in some feedback from the
ded to update each project, but this feels like it could be a
candidate for a goal for a future cycle once we have that information
and can assess the level of effort.
Doug
__
OpenStack Development Mailing List (not for usage question
Matt Riedemann writes:
> On 11/5/2018 1:36 PM, Doug Hellmann wrote:
>> I think the lazy stuff was all about the API responses. The log
>> translations worked a completely different way.
>
> Yeah maybe. And if so, I came across this in one of the blueprints:
>
> https
This is the weekly summary of work being done by the Technical Committee
members. The full list of active items is managed in the wiki:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
TC members,
I have updated the liaison assignments to fill in all of the
gaps. Please take a moment to review the list [1] so you know your
assignments.
Next week will be a good opportunity to touch bases with your teams.
Doug
[1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
_
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
I think the lazy stuff was all about the API responses. The log
translations worked a completely different way.
Doug
__
Doug Hellmann writes:
> Doug Hellmann writes:
>
> I asked the owners of the name "heat" to allow us to use it, and they
> rejected the request. So, I proposed a change to heat to update the
> sdist name to "openstack-heat".
>
> * https://review.openst
be managed through
the normal feature prioritization processes of the teams involved.
I will be moderating the discussion at the Forum, but I am not signing
up as a goal champion or to drive the goal selection. If you are
interested in helping with either of those things, please let me know.
Doug
[0
Doug Hellmann writes:
> TC members,
>
> The TC will be meeting on 1 Nov at 1400 UTC in #openstack-tc to discuss
> some of our ongoing initiatives. Here is the agenda for this week.
>
> * meeting procedures
>
> * discussion of topics for joint leadership meeting
Jeremy Stanley writes:
> On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> Did I miss any options or issues with this approach?
>
> https://review.openstack.org/578557
How high of a priority is rolling that feature out? It does seem to
eliminate this part
thought I ought to just go ahead and do this properly.
The patch in [2] is an example of how the releases repository can take
advantage of having a library like this.
Please add the series to your review queue.
Doug
[1] https://review.openstack.org/#/c/614597
[2] https://review.openstack.org
Doug Hellmann writes:
> z...@openstack.org writes:
>
>> Build failed.
>>
>> - publish-openstack-releasenotes-python3
>> http://logs.openstack.org/86/86022835fb39cb318e28994ed0290caddfb451be/tag/publish-openstack-releasenotes-python3/7347218/
>> : POST_FAILU
g
concern.
I think we should take option 3, and will be preparing a patch to do
that shortly.
Did I miss any options or issues with this approach?
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsub
| Champion |
+-+--+-+--+-++---++
| adjutant| 1/ 1 | - | +| 0 |
1 | 2 | Doug Hellmann |
| barbican| +| 1/ 3 | +| 1 |
1 | 7 | Dou
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
deliverable
** https://review.openstack.org/613856 Remove Dragonflow from the official
projects list
If you have suggestions for topics for the next meeting (6 Dec), please
add them to the wiki at
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions
Doug
ce Software
> Development Center ( https://kosslab.kr/ ).
>
>
> With many thanks,
>
> /Ian
>
> ___
> Community mailing list
> commun...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
This is an excellen
o add
> `openstack-python36-jobs` to the list that currently includes
> `openstack-python35-jobs` in each project's Zuul config[1], we'd have
> had a goal to change `openstack-python3-rocky-jobs` to
> `openstack-python3-stein-jobs` in each project's Zuul config.
os that
have issues, so please approve those quickly when they come in.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Each of those services has its own configuration file and database, and
the code is in separate repositories, so it seems like we would want a
separate upgrade check command for each one.
Doug
___
Monty Taylor writes:
> On 10/29/18 10:47 AM, Doug Hellmann wrote:
>> Monty Taylor writes:
>>
>>> Heya,
>>>
>>> Tobias and I were chatting at OpenStack Days Nordic about the Public
>>> Cloud Working Group potentially taking over as custodians o
o there's something
> to depend on) and gets proposed patches from zuul when new content is
> landed in openstack/vendor-profile-data.
>
> How's that sound?
I understand the benefit of separating the data files from the SDK, but
what is the benefit of separating the data files from
ean is going to propose empty patches with the
Sem-Ver instruction in the commit message to all of the repositories for
Stein deliverables that have stable/rocky branches.
Let us know if you have any questions.
Doug
[1]
http://lists.openstack.org/pipermail/openstack-operators/2018-October/0159
1 | 2 | Doug Hellmann |
| barbican| +| 1/ 3 | +| 1 |
1 | 7 | Doug Hellmann |
| blazar | +| + | +| 0 |
0 | 9 | Nguyen Hai |
| Chef
Trinh Nguyen writes:
> Thank Doug for coordinating this,
>
> Is there any way for us to update the health of the Searchlight project to
> reflect the current state? Right now the status is not good to attract new
> contributors.
When the new liaisons are assigned, please tal
Doug Hellmann writes:
> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period
Doug Hellmann writes:
> We have about 17 remaining patches to import zuul job settings into a
> few repositories. Those are mostly in stable branches and the jobs are
> failing in ways that may take us a long time to fix.
>
> Rather than waiting for those, Andreas and I are pr
Ken Giusti writes:
> On Tue, Oct 9, 2018 at 11:56 AM Doug Hellmann wrote:
>
>> Matthew Thode writes:
>>
>> > On 18-10-09 11:12:30, Doug Hellmann wrote:
>> >> Matthew Thode writes:
>> >>
>> >> > several projects have had p
Matthew Thode writes:
> On 18-10-09 11:12:30, Doug Hellmann wrote:
>> Matthew Thode writes:
>>
>> > several projects have had problems with the new release, some have ways
>> > of working around it, and some do not. I'm sending this just to raise
>> &
Ben Nemec writes:
> On 10/9/18 10:19 AM, Doug Hellmann wrote:
>> Brian Rosmaita writes:
>>
>>> On 10/8/18 11:59 PM, Matthew Thode wrote:
>>>> several projects have had problems with the new release, some have ways
>>>> of working around it,
nd
them.
If there's a way to add a fixture to oslo.messaging to support the tests
we can do that, too.
Doug
>
> [0] https://review.openstack.org/#/c/608196/
> [1]
> https://git.openstack.org/cgit/openstack/keystone/tree/keystone/tests/unit/common/test_notifications.py#n1343
>
> On
1 in, then there's
no rush to blacklist anything, is there?
> As far as the timing/content of 9.0.1, however, that may require further
> discussion.
>
> (In other words, I'm saying that when you say 'another solution', my
> position is that we should take 'ano
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Do you have links to the failure logs or bug reports or something? If I
wanted to
y.
>
> Thank you again, and remember that cycle-highlights should be
> submitted by RC1.
Thank you for everything, Anne! The cycle-highlights system you helped
us create is a great example of using decentralization and peer review
at the same time. I'm sure it's going to continue to be
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> Doug Hellmann writes:
>>
>>> I have filed requests with the maintainers of PyPI to claim the names
>>> "keystone" and "congress". That may
Abhishek Kekane writes:
> Hi Doug,
>
> Should I use something like SimpleHttpServer to upload a file and download
> the same, or there are other efficient ways to handle it,
> Kindly let me know if you are having any suggestions for the same.
Sure, that would work, especiall
would like to try to proceed before the end of the week.
Doug
+--+-+---++--+-+---+---+
| Subject | Repo
This is the weekly summary of work being done by the Technical Committee
members. The full list of active items is managed in the wiki:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
to manage the list
will be to wipe it and follow the same process we did last time. If you
agree, I will update the page this week and we can start collecting
volunteers over the next week or so.
Doug
[1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
TC members,
I have some PTO planned, so I will be away from 13 Oct - 28 Oct. I
approved the patch appointing Mohammed as vice chair this morning, so he
will be serving as chair during that time.
Doug
__
OpenStack
me know if you foresee any issues with that plan.
Doug
[1] https://review.openstack.org/608682
[2] https://review.openstack.org/608680
[3] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
__
OpenStack Development
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> I think we are ready to go ahead and switch all of the python packaging
>>> jobs to the new set defined in the publish-to-pypi-python3 template
>>> [1]. We still hav
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> I think we are ready to go ahead and switch all of the python packaging
>> jobs to the new set defined in the publish-to-pypi-python3 template
>> [1]. We still have some cleanup patches for projects that have not
Watch for changes in pip's behavior. - Doug
Pradyun Gedam writes:
> On behalf of the PyPA, I am pleased to announce that pip 18.1 has just
> been released.
>
> To install pip 18.1, you can run::
>
> python -m pip install --upgrade pip
>
> or use get-pip as described
y release, so I don't really see any reason to create
the branch. There isn't anything to maintain.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
Chris Dent writes:
> On Thu, 4 Oct 2018, Doug Hellmann wrote:
>
>> TC members, please reply to this thread and indicate if you would find
>> meeting at 1300 UTC on the first Thursday of every month acceptable, and
>> of course include any other comments you might h
Thierry Carrez writes:
> Ghanshyam Mann wrote:
>> On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley
>> wrote
>> > On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote:
>> > [...]
>> > > TC members, please reply to this t
supported in another, running a different version of the
same service?
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
s serving files as part of the test setup.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/m
Trinh Nguyen writes:
> Thank Jeremy, Doug for explaining.
>
> On Fri, Oct 5, 2018 at 6:54 AM Doug Hellmann wrote:
>
>> Jeremy Stanley writes:
>>
>> > On 2018-10-04 23:11:22 +0900 (+0900), Trinh Nguyen wrote:
>> > [...]
>> >> Please
Jeremy Stanley writes:
> On 2018-10-04 17:57:06 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> HTTPError: 400 Client Error: Invalid value for classifiers. Error:
>> 'Topic:: Utilities' is not a valid choice for this field for url:
>> https://upload.pypi.org/lega
Stephen Finucane writes:
> On Thu, 2018-10-04 at 07:21 -0400, Doug Hellmann wrote:
>> Stephen Finucane writes:
[snip]
>> > Anyway, we can go figure out what's changed here and handle it but this
>> > is, at best, going to be a band aid. The fact is 'sphinx_te
an
upload. If someone knows of a way, please let me know.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
equired in order to produce releases with the
automation in the short term.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
onth acceptable, and
of course include any other comments you might have (including alternate
times).
Thanks,
Doug
[1]
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-10-04.log.html#t2018-10-04T15:02:31
[2] https://www.openstack.org/legal/technical-com
and bring it up-to-date. Maintain
>forever.
> * Start using 'sphinx.testing' and everything it comes with
> * Delete any tests that use 'sphinx_testing' and deal with the lack of
>coverage
Could we change our tests to use pathlib to wrap app.outdir and get the
same r
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> == Things We Learned This Week ==
>>>
>>> When we updated the tox.ini settings for jobs like pep8 and release
>>> notes early in the Rocky session we on
of the work done by the first
milestone, and I think we're close enough to do it. Please look through
the list of patches for your project and ensure they are in your review
queues.
Thanks,
Doug
[1]
https://review.openstack.org/#/q/topic:python3-first+is:open+message:%22import+zuul+job+settings
AdityaVaja writes:
> Hello Doug,
>
> I was going to send out an email or drop in on IRC to check how to fix that.
>
> We accidentally pushed 13.0.1 on stable/queens, instead of 12.0.5. (13.x.x
> is rocky and 12.x.x is queens)
> Tried reverting the situation by pushing 12.0.
ils, Wes. I know the current situation has
been hurting the TripleO team as well, so I'm glad to see a good plan in
place to address it. I look forward to seeing updates about the
progress.
Doug
__
OpenStack Developmen
Zane Bitter writes:
> On 3/10/18 9:42 AM, Matt Riedemann wrote:
>> On 10/3/2018 7:58 AM, Doug Hellmann wrote:
>>> There is one more patch to import the zuul configuration for the
>>> heat-agents repository's stable/ocata branch. That branch is apparently
>
story requires a target version of
pbr.version.SemanticVersion(13.0.1), but target version is
pbr.version.SemanticVersion(12.0.5)
This is being caused by re-tagging the 13.0.1 release as 12.0.5.
I think if we tag a *newer* commit as 12.0.6 that will work (i
-config, so I would like to get a definitive answer about what to
do. Should we close the branch, or does someone want to try to fix
things up?
Doug
[1] https://review.openstack.org/#/c/597272/
__
OpenStack Development Mailing
| Champion |
+-+-+--+-+--+-++---++
| adjutant| + | 1/ 1 | - | +
| 0 | 1 | 6 | Doug Hellmann |
| barbican| 7/ 13 | +| 1/ 3 | +
| 6 | 4 | 20 | Doug Hellmann
Miguel Angel Ajo Pelayo writes:
> Thank you for the guidance and ping Doug.
>
> Was this triggered by [1] ? or By the 1.1.0 tag pushed to gerrit?
The release jobs are always triggered by the git tagging event. The
patches in openstack/releases run a job that adds tags, but the patch
y
Dariusz Krol writes:
> Hello Doug,
>
> thanks for your explanation. I was a little bit confused by changes to
> stable branches with python3-first topic as I thought it has to do
> something with adding new test configuration for python3.
>
> But as you explained this
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> == Things We Learned This Week ==
>>
>> When we updated the tox.ini settings for jobs like pep8 and release
>> notes early in the Rocky session we only touched some of the official
>> repositories. I'll be
Jeremy Stanley writes:
> On 2018-09-28 13:58:52 -0400 (-0400), William M Edmonds wrote:
>> Doug Hellmann wrote on 09/26/2018 06:29:11 PM:
>>
>> > * We do not want to set the override once in testenv, because that
>> > breaks the more specific versions
Doug Hellmann writes:
> I think we are ready to go ahead and switch all of the python packaging
> jobs to the new set defined in the publish-to-pypi-python3 template
> [1]. We still have some cleanup patches for projects that have not
> completed their zuul migration, but there ar
ches to the stable branch. See
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133594.html
for details.
Doug
> I hope this helps.
>
>
> Best,
>
> Dariusz Krol
>
>
> On 09/27/2018 06:04 PM, Ben Nemec wrote:
>>
>>
>> On 9/27/18 10:36 AM
z...@openstack.org writes:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/d4/d445ff62676bc5b2753fba132a3894731a289fb9/release/release-openstack-python/629c35f/
> : FAILURE in 3m 57s
> - announce-release announce-release : SKIPPED
> - propose-update-constraints
Emmet Hikory writes:
> Please join me in congratulating the 6 newly elected members of the
> Technical Committee (TC):
>
> - Doug Hellmann (dhellmann)
> - Julia Kreger (TheJulia)
> - Jeremy Stanley (fungi)
> - Jean-Philippe Evrard (evrardjp)
> - L
ut how
that list is managed in the project team guide at
https://docs.openstack.org/project-team-guide/dependency-management.html
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
Dariusz Krol writes:
> Hello Champions :)
>
>
> I work on the Trove project and we are wondering if python3 should be
> supported in previous releases as well?
>
> Actually this question was asked by Alan Pevec from the stable branch
> maintainers list.
>
> I saw you added releases up to ocata
enough.
The template adds a new check job that runs when any files related to
packaging are changed (readme, setup, etc.). Otherwise it switches from
the python2-based PyPI job to use python3.
I have the patch to switch all official projects ready in [2].
Doug
[1]
http://git.openstack.org/cgit
thon-*client, but it's important and
> we just need to all be on the same page.
That sounds like a reason to keep the governance of the libraries under
the client tool project.
Doug
__
OpenStack Development Mailing List
on-openstackclient depend on them, and then asking project teams for
more help with them.
> One thing I don't like about that is we just replace N client libs
> with N (or more) plugins now and the number of things a user must
> install doesn't go down. I would like to hear from anyone who
Doug Hellmann writes:
> == Things We Learned This Week ==
>
> When we updated the tox.ini settings for jobs like pep8 and release
> notes early in the Rocky session we only touched some of the official
> repositories. I'll be working on making a list of the ones we missed so
>
Monty Taylor writes:
> On 09/26/2018 01:55 PM, Tim Bell wrote:
>>
>> Doug,
>>
>> Thanks for raising this. I'd like to highlight the goal "Finish moving
>> legacy python-*client CLIs to python-openstackclient" from the etherpad and
>> propose t
th the fact that the project name is
> stevedore but the bug link is python-stevedore? I'm not sure why that
> is, but there may be something a little weird going on with that
> project.
The name "stevedore" was taking on LP when I registered that
s, we will
know that the job is working in general based on other releases
(including more liberal use of our test repository before big
deadlines).
Doug
__
OpenStack Development Mailing List (not for usage que
.
Doug
[1] https://etherpad.openstack.org/p/community-goals
[2] https://www.openstack.org/summit/berlin-2018/vote-for-speakers#/22814
[3] https://governance.openstack.org/tc/goals/index.html
__
OpenStack Development Mailing
| Champion |
+-+-+--+-+--+-++---++
| adjutant| + | -| - | +| 0 |
0 | 5 | Doug Hellmann |
| barbican| 11/ 13 | +| 1/ 3 | +| 6 |
4 | 20 | Dou
Adam Coldrick writes:
> On Mon, 2018-09-24 at 22:47 +, Jeremy Stanley wrote:
>> On 2018-09-24 18:35:04 -0400 (-0400), Doug Hellmann wrote:
>> [...]
>> > At the PTG there was feedback from at least one team that
>> > consumers of the data in storyboard wan
Jeremy Stanley writes:
> On 2018-09-24 18:35:04 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> At the PTG there was feedback from at least one team that
>> consumers of the data in storyboard want a priority setting on
>> each story. Historically the response to that ha
er that position if it's going to block
adoption. I think Ben's case is an excellent second example of where
having a field to hold some sort of priority value would be useful.
Doug
__
OpenStack Development Mailing List
Doug Hellmann writes:
> Earlier today a bad version of twine (1.12.0) caused issues with many of
> the release jobs that were trying to publish artifacts to
> pypi.python.org. I didn't notice those failures until after all of the
> releases had been processed, unfortunately, w
of that, we're going to re-tag the releases,
using new version numbers, to produce good artifacts. I have prepared
https://review.openstack.org/#/c/604875/ to do this.
I will also run some tests to ensure the publishing works before
approving those re-releases.
Sorry for the inconvenience,
Doug
-to-pypi-python3 template which
runs a job that uses python 3. See [1] for an example.
Doug
[1] https://review.openstack.org/#/c/598323
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opens
Melvin Hillsman writes:
> On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann
> wrote:
>
>> Maybe we're overthinking the organization on this. What is special about
>> the items that would be on this list compared to items opened directly
>> against projects?
>>
d reports about the open and unreleased changes,
> that could be a useful input for the before-EM/final release.
> Please have a look at the report (and review the open patches if there
> are) so that a release can be made if necessary.
>
> Thanks,
>
> Előd
Thanks for pu
series goals, and
making decisions that have long term effects on the project.
Please take a few minutes to look at Kendall's instructions[1],
find your ballot email, and think about which candidates you want
to have on the committee. Then cast your vote, today.
Doug
[1]
http
1 - 100 of 3644 matches
Mail list logo
