Hi everybody,
as you all know, we have the openSUSE Members, a group of contributors through
their sustained and substantial contributors that are eligible to participate
in elections, have @opensuse.org mail and other perks. We have now about 600
of them, but as you can see[1] in last openSUSE Board elections only 150 of
them voted.
This could mean two things - either most of the members are not interested in
elections or plenty of them are simply no longer around. I guess the truth is
somewhere in middle. This is something we need to know when we take project
wide decisions in order to correctly assess the communities interest in the
topic.
This is a recurring topic that has been discussed at the openSUSE Board Face to
Face meeting last year, oSC 15, and on this list several times over the last
few years. Taking these into consideration, we (in the board) think it would
be a good idea to implement something to help with ensuring our Membership list
accurately reflects our current Membership. I have put together a tool which
attempts to detect an openSUSE Members activity on mailing lists, OBS,
bugzilla, maybe more. This tool will remember when we last saw openSUSE Member
on any of those channels and if they doesn't show for 6 months, we will send
them an e-mail asking whether they still wants to be a member. A response to
that email will automatically count as activity and preserve the Members
status. If there is no response within 30 days of the notification, the Member
will be 'retired' and be considered a 'Member emeritus'. If someone is retired
incorrectly, or a 'Member emeritus' returns to the Project and wants a
restoration of their voting privilege, they will be unretired without question
by the Membership Committee.
There are few implementation details to be worked out, so we don't expect this
to go live overnight but consider this a "statement of intent" and an
explanation of how we expect things to work before we start testing the
process.
====
To answer some of the obvious questions:
Q: Shouldn't we retire inactive members anyway after measuring and evaluating
their activity?
A: No, that would be too hard, too subjective and it could bother people that
we cannot measure automatically. Automatic measurement is just an indicator
that those people are no longer interested, but they might be just working
on project aspects we cannot measure. openSUSE Members are members until
THEY no longer want to be. We believe this system preserves that principle.
Q: Wouldn't it offend active contributors if they will be falsely accused of
not being interested?
A: I hope not. If period will be long enough (6 months) and if we monitor even
mailing lists, people will usually show up somewhere. We intend to word the
'ping' email in a way that is not judgemental, but just makes it clear that
we have failed to automatically find evidence of contribution so want to make
sure they are still interested in remaining a Member.
Q: Doesn't it change the meaning of the openSUSE Member?
A: Not really. So far once you got a membership status, it was forever without
question. Now it would be forever as long as you are interested. No big
change, just a little difference.
Q: What if mail with warning gets lost?
A: If you lose your membership by accident by losing an e-mail, you can still
contact membership committee and as a retired member you will be reinstated
immediately without voting/verification that takes time. And you should fix
your e-mail in connect.opensuse.org in that case ;-)
Q: Will retired members retain their email & IRC cloak perks?
A: No, the intention is that retired members will no longer be eligible for
@opensuse.org email addresses and Freenode IRC cloaks.
[1] https://connect.opensuse.org/pg/polls/read/pluskalm/49480/opensuse-board-el…
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Greeting fellow Geekos!
As you know lots of new stuff are coming in the future of the project!
It has occcured to me during conversations with fellow linux users
that though openSUSE is among the leading distros , help towards
technical (or other) problems still needs improvement. Quite a few
people are asking question on the facebook group, and most of them are
answered thoroughly, but we are not archived or reachable from
non-facebook users and the forum traffic is low. So I wonder is it
possible to have an official stack exchange page where users can ask
for help? What are the difficulties we might face?
Imho it would be more efficient and new users will appreciate it more.
Care to share your thoughts on what can be done? I'm willing to help
if we reach an agreement
inb4: I'm not saying to close the forum
--
Nick Mantas
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
We will have our last organizing meeting for this year's openSUSE
Conference on the opensuse-project channel on freenode IRC today at 1700
UTC.
The topics we will discuss in today's meetings are:
Keynote Changes
Proposals Status
Daily emails
Equipment update
Volunteers
Make sure to register for the social events under “My Registration” on
events.opensuse.org if you want to attend any of the city or cellar
tours in Nuremberg.
Presentation template -
https://progress.opensuse.org/attachments/download/1348/openSUSE%202015%20T…
v/r
Doug
Hi all,
I'm wondering how to tackle an issue with the crash utility and its
eppic extension.
I'd like to build crash-eppic as a subpackage of eppic, because that's
where the source code is maintained by upstream these days. The trouble
is that crash-eppic is now a subpackage of the crash package, which is
at version 7.1.5. There is no versioned release of eppic, but the
upstream maintainer told me that the next versioned release would be
4.0, so I can safely use a bogus version of 3.99.$something for the
libeppic package.
I'm unsure what to do about the version of crash-eppic. If it inherits
the version number from eppic, it would be downgraded from 7.1.5 to
3.99.$something. I assume this is a problem for Tumbleweed. If I keep
7.1.5 as the version number, then it's a completely arbitrary one - it
would merely indicate the last crash version where the extension was
built from the incorrect sources.
I could probably change the version if I name the package differently,
but "crash-eppic" is in fact the perfect name, as there are other crash
extensions named "crash-something".
FTR Fedora doesn't seem to package crash extensions...
Any ideas are welcome!
Petr T
P.S. Some background if you want to ask how we ended up in this
situation:
Originally, the eppic extension was part of the
upstream crash tarball. Consequently, crash-eppic was built as a
subpackage of the crash package.
At some point, upstream development of eppic was split off (see
https://github.com/lucchouina/eppic). This repo now contains the
library (which is also used by other projects, e.g. makedumpfile) and
the crash extension code.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
# Board Meeting Minutes 30 May 1600 CEST
## Present
- Richard Brown - Chair
- Michal Hrušecký
- Kostas Koudaras
- Bryan Lunduke
## Absent
- Tomas Chvatal - Apartment move
- Gertjan Lettink - House move
- Andrew Wafaa (Treasurer) - Bank Holiday
## General Items
### openSUSE Asia
The Board recieved an exceptional bid from the Indonesia Team. The
Board discussed the bid over email and again during the meeting. It's
Approved - openSUSE Asia should happen later this year in Indonesia.
### oSC 16
Planning all going smooth. Full program is published
https://events.opensuse.org/conference/oSC16. The Board is very
pleased to see a very wide range of talks covering talks across the
whole spectrum of Linux, Distributions, DevOps, Cloud and Storage.
### TSP
The Board understands all TSP requests for oSC 16 have been approved
with the applicant notified.
### Hackweek
SUSE have confirmed their Hackweek will start on Friday 24th (at oSC)
and carry over into the next week, 27-01. The Board would like to
invite all SUSE employees to use at least part of this extra hackweek
day on the 24th to visit oSC and use it to get ideas for the rest of
Hackweek. Fridays program includes talks about ARM, btrfs, Docker,
Ceph, KDE, Machinery, CI and more, including two awesome talks about
openQA (one from Christopher Hoffman and another by the author of
these minutes who really shouldn't misuse this platform to advertise
his session but I wonder if anyone is reading this anyway ;)). Friday
evening also has a performance of the SUSE Band
### Trademark Request
The Board have heard from the members with the outstanding Trademark
request. Local legal requirements complicate our proposed solution.
Negotiations ongoing.
### Membership Tidyup
The first round of the Membership reminder/tidy emails have been sent.
268 members were pinged with an email asking htem to respond if they
still interested in being a member. 70 responses came from Mail
Delivery System. If you think you could be one of those 70 please
update your contact details on https://connect.opensuse.org or else
you will not recieve future reminders. A few dozen human responses
have already been recieved. Those peoples openSUSE Memberships are now
secured and will no longer recieve reminders until the next round of
membership cleanup.
### Infrastructure
The Board remains concerned about ongoing Infrastructure issues. Board
notes that some efforts have been made to improve the situation with
www.opensuse.org and other Provo hosted openSUSE services, but would
like to see a sustainable long term solution.
The Board is also concerned by the long lead time on tickets to
admin(a)opensuse.org.
AI: Richard to have meeting with Roland.
### SLE Packages
The Board has spotted a number of cases in Leap 42.2 Alpha 2 where
packages inherited from SLE are newer than the ones available in
Tumbleweed or Devel Repos.
AI: Richard has send both general and directed reminders internally at
SUSE to remind them of the SUSE company policy to contribute to
Tumbleweed before/in parralel/in sync with their work on SLE.
## Action Item Review
Due to the large number of action items, the progress of these will be
split into 3 sections
- DONE; This task is complete and will not be discussed in future meetings
- WIP; This task is in progress, and will be discussed in future meetings
- TODO; This task is still waiting for some progress by the Board
### DONE
Michal has started the bot to contact missing members to see if they
wish to retain their openSUSE membership.
openSUSE Asia team submitted their proposal.
Andrew completed the first round of TSP approvals for oSC.
### WIP
Board + Ludwig to figure out what to do with all the Volunteers for
the "openSUSE Release Team"
*Richard & Ludwig to discuss*
Board is discussing some ideas with our various Desktop Teams
Michal is retiring connect.opensuse.org and doing the Membership
tooling and maintenance.
Tomas has talked with Craig about OBS team preparing the code for
maintaner tidyup
*Feature in OBS teams TODO*
Bryan has started arrange informal exploratory discussions with
ownCloud and Kolab about closer relationships
*Meetings expected at oSC*
Kostas is reaching out to our few bloggers on lizards.opensuse.org
about moving to other platforms.
Richard has been talking to Douglas about the possibility of moving
news.opensuse.org to a new blogging platform. Richard's personal blog
is running a potential candidate (Jekyll with custom openSUSE theme)
http://rootco.de
### TODO
Board to request release-team(a)opensuse.org list for the Release Team
Board to investigate alternatives for voting & membership management
_To be done after the Membership Tidy Up_
Tomas will investigate Helios voting system for openSUSE
Richard to review/tune up filtering in current system so trademark
enquiries don't get lost
Tomas will talk with Andrew and Marketing teams about possible Kickstarter
Board intends to create a skeleton of the getting started guides to
help people get started with Using, Joining, and Partnering with
openSUSE
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Buenas tardes, mi nombre es Juan esteban Vásquez
Vivo en Colombia y actualmente lidero una empresa de infraestructura
informàtica donde estamos incursionando en Linux. Previamente estuve
estudiando varias distribuciones y me encontré con Opensuse Leap 42.1 la cual
me sorprendió impresionantemente en aspectos como la organizaciòn de la
comunidad, el aspecto visual y aspectos leidos en la parte técnica. Tengo a mi
cargo personal técnico para comenzar a trabajar con este proyecto y poder
aportar en lo que mas podamos. Nuestros clientes son las empresas y buscamos
fortalecer, opinar, capacitarnos y quizas impulsar este gran proyecto de la
mano de ustedes.
Somos Soporte Efectivo SAS y queremos acompañar y ser acompañados por este
gran proyecto Open Source en dar soluciones para empresas.
Saludos y quedo atento.
Juan Esteban Vásquez Sánchez
Soporte Efectivo SAS
www.soporteefectivo.com
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Good morning,
quick question...will we have a kind of blackboard or mailing list for the oSC16 participants, e.g. to announce travel / rooms available?
Best regards
Axel
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
We will have an organizing meeting for the openSUSE Conference on the
opensuse-project channel on freenode IRC today at 1700 UTC.
The topics we will discuss in today's meetings are:
Proposals
Scheduling
Marketing Status
Trello Cards
Equipment update
Swag update
other
Make sure to register for the social events under “My Registration” on
events.opensuse.org if you want to attend any of the city or cellar
tours in Nuremberg.
After May 30, all unconfirmed proposals will be cancelled.
Presentation template -
https://progress.opensuse.org/attachments/download/1348/openSUSE%202015%20T…
v/r
Doug
Hi all,
We will have an organizing meeting for the openSUSE Conference on the
opensuse-project channel on freenode IRC today at 1700 UTC.
Those giving proposals who do not already have a template (company or
project) are asked to use the openSUSE Presentation template at
https://progress.opensuse.org/attachments/download/1348/openSUSE%202015%20T…
Please confirm your proposal by May 30 so we can create a printed schedule.
The topics we will discuss in today's meetings are:
Accepted Proposals
Marketing Status
Keynote Update
MC
Trello Cards
Start Scheduling
Equipment update
Swag update
v/r
Doug
# Board Meeting Minutes 16 May 1600 CEST
## Present
- Richard Brown - Chair
- Michal Hrušecký
- Tomas Chvatal
- Gertjan Lettink
- Andrew Wafaa
## Absent
- Kostas Koudaras - Family Bereveament
- Bryan Lunduke
## General Items
### Travel Support Programme
We have 13 Applications for oSC 16. 3 of them from GSoC students, 1
from a GSoC Mentor.
Budget forecasts look promising, so we expect to be able to sponsor
them all, though the exact level is still to be determined.
AI: Andrew to confirm some details with Izabel
### Infrastructure
Board is concerned about ongoing Infrastructure issues. Board notes
that some efforts have been made to improve the situation with
www.opensuse.org and other Provo hosted openSUSE services, but would
like to see a sustainable long term solution.
The Board is also concerned by the long lead time on tickets to
admin(a)opensuse.org.
### openSUSE Asia
The Board have seen a draft of a proposal for openSUSE Asia.
Proposal looks good, but we are waiting feedback on a few points
AI: Richard to Chase.
### Trademark request
The Board is still waiting for response about possible compromise
agreement for outstanding Trademark request.
## Action Item Review
Due to the large number of action items, the progress of these will be
split into 3 sections
- DONE; This task is complete and will not be discussed in future meetings
- WIP; This task is in progress, and will be discussed in future meetings
- TODO; This task is still waiting for some progress by the Board
### DONE
Board to put stuff on wiki regarding rules/scope of Treasurer
*Gertjan to take care of this by the next meeting*
### WIP
Board + Ludwig to figure out what to do with all the Volunteers for
the "openSUSE Release Team"
*Richard & Ludwig to discuss*
Board is discussing some ideas with our various Desktop Teams
Michal is working on tooling and the process of retiring members
*Nice, friendly, contact emails have been drafted, first experiments
will be soon*
Michal is retiring connect.opensuse.org and doing the Membership tooling
Tomas has talked with Craig about OBS team preparing the code for
maintaner tidyup
*Feature in OBS teams TODO*
Bryan has started arrange informal exploratory discussions with
ownCloud and Kolab about closer relationships
*Meetings still expected in the next week or two*
Kostas is reaching out to our few bloggers on lizards.opensuse.org
about moving to other platforms.
Richard has been talking to Douglas about the possibility of moving
news.opensuse.org to a new blogging platform. Richard's personal blog
is running a potential candidate (Jekyll with custom openSUSE theme)
http://rootco.de
### TODO
Board to request release-team(a)opensuse.org list for the Release Team
Board to investigate alternatives for voting & membership management
_To be done after the Membership Tidy Up_
Tomas will investigate Helios voting system for openSUSE
Richard to review/tune up filtering in current system so trademark
enquiries don't get lost
Tomas will talk with Andrew and Marketing teams about possible Kickstarter
Board intends to create a skeleton of the getting started guides to
help people get started with Using, Joining, and Partnering with
openSUSE
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
