Hi all,
I have one easier topic to discuss.
We already have several cases where it would be useful to have a general
email address for the "team". For example, in deb packing files, Tim is
specifically listed as the "Maintainer:" with his address, while it would
be more appropriate to use the general "deb team" address. Similarly for
Gentoo packaging it would be useful to have an email address for the
Gentoo team.
Here are three ways to create such addresses:
1. An alias that ensures delivery of emails to a manually maintained list
of recipients.
This is a simple solution, but it can run into a problem due to SPF/DKIM
and at the same time it does not provide much comfort in answering - so
that other team members are informed as well.
2. Mailing list open to all for incoming mails and with a moderated
subscription.
There is good comfort for subscribing team members, it handles replying to
a mailing list well and can provide an archive - it is possible to choose
whether private or public.
3. Shared mailbox for each team.
A full IMAP mailbox is good - all emails in one place, but it has the
disadvantage of having to share a password.
What way do you think is best?
Cheers
--
Slávek
...when these settings are used in tdmrc in openSUSE 15.2:
SelectedUsers=root,me
HiddenUsers=
UseTheme=false
Theme=
PreselectUser=me
FocusPasswd=true
LoginMode=DefaultLocal
Users list with no user preselected is a real problem, because user "me" is really
my 90 year old mom. She can manage the password when it's the default, but I don't
seem to be able to make it the default. Am I overlooking something? Or, is this a
bug nobody notices because everybody uses the mousetype default theme or autologin?
--
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi,
I did upgrade freshly compiled 14.1, but hit the one in the Subject.
Subsequent "apt-get -f install" solved it (I hope).
Removing 'diversion
of /opt/trinity/share/apps/konqueror/servicemenus/media_safelyremove.desktop
to /opt/trinity/share/apps/konqueror/servicemenus/media_safelyremove.desktop.distrib
by tdeio-umountwrapper-trinity'
Removing 'diversion
of /opt/trinity/share/apps/d3lphin/servicemenus/media_safelyremove.desktop
to /opt/trinity/share/apps/d3lphin/servicemenus/media_safelyremove.desktop.distrib
by tdeio-umountwrapper-trinity'
rmdir: failed to remove '/opt/trinity/share/apps/d3lphin/servicemenus/': No
such file or directory
dpkg: error processing package tdeio-umountwrapper-trinity (--configure):
installed tdeio-umountwrapper-trinity package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
tdeio-umountwrapper-trinity
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hi all,
with the arrival of the new year, in addition to wishing you good health
and well-being, I open another topic for discussion - arrangement
between the project and contributors.
As with many other open source projects, there were concerns about
patent trolls and other potential legal risks that led Tim to propose
the use of a CLA (Contributor License Agreement) in 2014. The questions
following the CLA's proposal were mainly technical and focused on how to
confirm compliance with these arrangements for smaller contributors. The
discussion that followed led to a consensus on the fact that it was
essential for the contributors to add a "Signed-off-by:" line to their
contributions.
As a result, the "Signed-off-by" requirement is exactly the same as the
one for the DCO (Developer Certificate of Origin). DCO is significantly
simpler than a CLA and now used by a lot of open source projects. For
these reasons, in recent years we have already been using DCO rather
than CLA for all contributions made.
We would like to officially declare the CLA obsolete and replace it by a
DCO. This would actually officially reconcile the declared state and the
way it is actually used. Therefore, I ask you if anyone is aware of any
obstacles, why this could not be done?
See the CLA discussion thread:
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
See DCO:
https://developercertificate.org/
Cheers
--
Slávek
