Hi all,
after reading https://en.opensuse.org/openSUSE:Members, I understand that I can cancel my membership status with
immediate effect and forever.
To become a "Member Emeritus", with a "way back" into the community in case things might turn good again, I have to wait
for the status request and just not respond to it. But the last such request was almost 3 years ago. IIUC I need to stop
all actions on the mailing lists (might be a good idea ;-)) and packaging (not so good) for the bot to pick me up.
So is there a manual procedure to follow to become "Member Emeritus"?
Best regards,
Stefan
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt
<Lars.Vogdt(a)suse.com>:
As such, maintaining 447 [1] openSUSE members should not depend on a
single tool. Especially not if the used tool has open, well known
security issues since years[2].
On Thu, 21 Feb 2019 11:41:19 +0100 Richard Brown wrote:
> This isn't the first time I've asked this question on a public stage,
> but in the hope that this time I get an answer;
> Who volunteers to tackle the problem with connect.o.o and drive
> forward a solution?
I made my proposal already and I stand the point: shut down an insecure
system!
what does "drive forward a solution" mean? Can we integrate the
functions of connect.o.o into other services at openSUSE which are
allready maintained like the openSUSE wiki? A form for travel support
for example?
An application for membership could be done by e-mail to an e-mail
address of the membership officials. Elections could be done with an
eVote software like https://github.com/mdipierro/evote for example, but
probably there are better tools.
What did I miss?
I think Lars is right an we should shutdown this insecure system as soon
as possible.
Regards
Christian Imhorst
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On the board meeting two hours ago we discussed adding an
"abstain" option to future votes. We unanimously agreed.
That is, future votings shall include "abstain" as a choice.
Thank you to all who provided feedback!
Gerald
PS: We understand board elections allow a flexible number of
choices, including choosing no candidate, so we do not see
this as applicable there.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
Since the current NNTP gateway by MicoFocus is being shutdown from Wed 19th of
June, there will temporarily be none. Meanwhile some of our community members
are working on replacing it, announcements about this will follow a.s.a.p.
--
Gertjan Lettink a.k.a. Knurpht
openSUSE Board Member
openSUSE Forums Team
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Dear Community,
The openSUSE Board election is knocking at our door and we need to form
the next Election Committee in order to plan and oversee the smooth
running of this election.
As the Board election rules [1] state, the Election Committee should
consist of at least two openSUSE members.
Gerry Makaro, volunteered greatly and dedicated much of his time in the
planning of the Board election 2018 - 2019. However, he won't be
available to help this time. His meticulous planning will be greatly missed.
Currently, the Election Committee has two members, Edwin Zakaria and
myself. This is the strict minimum that the Board election rules
specify. It also means that there is a huge amount of work to be done in
a short lapse of time.
Therefore, we are calling for volunteers, who wish to join the Election
Committee and help with the election planning.
Note that by joining the Election Committee you won't be eligible to run
as Board candidate.
Regards,
Ish Sookun
[1] https://en.opensuse.org/openSUSE:Board_election_rules
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello,
here are the minutes of the 2019-11-12 board meeting.
If you prefer a more formatted way, you can also read them on
https://en.opensuse.org/Archive:Board_meeting_2019-11-12
Present: Gertjan, Simon, Axel, Gerald, Christian
Absent with notice: Marina
== Name vote ==
* the board is happy that we got a clear result
* future votes will always have an abstain option (Action: Gerald will
announce this on the project ML)
== openSUSE trademarks ==
* Gerald will ask SUSE Legal to write a contract draft for the openSUSE
trademarks so that the foundation can use them.
* the contract should allow long-term / permanent permissions to use the
trademarks
* ideally, transfering the trademarks to the foundation in the future
should be possible
== Forum move ==
* we are still waiting for the forums database dump. Gerald will
escalate this with MF-IT.
== misc ==
* Gerald is invited to a EU panel discussion in Brussels, he'll send the
questions to board@ to get some input
* Simon reported that kangaroos enjoy having fun[tm] with cars (running
into or jumping onto them), and aren't easy to cook
Regards,
Christian Boltz
--
Bei etwas größeren Dingen mit 6stelligem Budget kommt gern mal
"plötzlich" ein Onlineshop dazu. Oder ein Ticketsystem. So ganz
von alleine. Gucki, ich bin eine kleine Kundenidee - ist das viel
Arbeit? ;) [Ratti in suse-linux]
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
I think I've already posted about this, but I think there really needs
to be done something.
About 75% or even more of the spam I'm getting arrives at my
opensuse.org email, and on closer inspection has been directly delivered
to the secondary MX for opensuse.org.
I take that spam, and feed it through spamcop.net which results in a
complaint being sent to postmaster(a)suse.de, and I am getting the feeling
that no one reads mails to that address, because in I don't know how
many years I have gotten not a SINGLE reaction.
>From the behaviour of "the system I can draw two conclusions:
1. that MX has no spam filter capabilities what so ever, not even
something as simple as dns based block lists
2. no one gives a shit.
I have already posted on that suse internal tracker thing that was
suggested to me last time I said anything - and also no real reaction
other than someone answering in a truly noncommital way, see
https://progress.opensuse.org/issues/55838
so ... can I have some numbers about the mail volume on the opensuse.org
domains? do we have to deal with the mail servers for opensuse.org
ourselves?
I mean, there is so much that *can* be done, spamassassin *with* DNS
blacklists, postgrey, you name it.
Cheers
MH
--
*Mathias Homann*
Mathias.Homann@openSUSE:.org
irc: [Lemmy] @ freenode, ircnet
obs: lemmy04
keybase: https://keybase.io/lemmy
*gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102*
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Dear all,
The vote has ended and the results have been released.
Do we change the project name?
Yes 42
No 225
Regards,
Ish Sookun
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi list,
do we have a policy how to address dead upstream projects from the
openSUSE project?
I have submitted a pull request to the openSUSE/vagrant project 3 months
ago to replace it's current state with a set of new build recipes that
I've been working on and that are now used to build the official
Tumbleweed Vagrant box on Vagrant Cloud. Unfortunately, the project
appears to be dead properly (afaik the main maintainer does no longer
work for SUSE) and my pull request has only been reviewed by external
contributors.
Can we do something about this? I'd be willing to (co-)maintain this
project, so that the build recipes can finally be public. Or I'd request
a new project to be created and archive openSUSE/vagrant instead?
Cheers,
Dan
--
Dan Čermák <dcermak(a)suse.com>
Software Engineer Development tools
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany
(HRB 36809, AG Nürnberg)
Managing Director: Felix Imendörffer
Hi list,
after a lot of energy put into a voting and a lot of time spent in
writing mails to fill up my opensuse-project folder, everyone of the
super active participants in this discussion I would like to see a talk
submission for next openSUSE Conference or Summit near you or getting
any other task for the project done.
On my to do list for this weekend:
- Trying to find a sponsorship for rsync.o.o, as discussed in Heroes
meeting on Tuesday.
- Thinking about how we finally solve the rsync.o.o fun.
Let the work speak for itself for some time now and let's reduce the
flood of mails.
openSUSE - Alles bleibt so wie es ist...
- everything stays the same...
Best regards
--
Thorsten Bro <tbro(a)opensuse.org>
- Member of openSUSE Heroes -
https://en.opensuse.org/openSUSE:Heroes
- Member of openSUSE VideoTeam -
https://en.opensuse.org/openSUSE:Video
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org