WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Extension maintainership  (Read 8840 times)

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9330
Extension maintainership
« on: March 07, 2010, 03:10:53 AM »
When updating an extension originally made by someone else, one needs to contact the original extension maker with the intention to update or fix it.  Usually a request for an extension to be updated can be made in the extension's TCE News thread and the extension maintainer will update it or give the go-ahead for it to be updated.  If the original extension maker cannot be contacted in either PM or in the forum and a week goes by after announcing the intentions in the extensions news thread, then one can proceed with an update.  Even if the original extension maker appear to be inactive it is good to at least try to contact them.  On the unusual and not seen before chance that an extension maintainer will not update an extension and will not allow it to be updated, I or another team member will get involved and if the extension is holding up the repo's progress by not being updated I or another team member will overrule the original extension maker and allow the update.  I don't think that will ever happen, but I had to throw it in just in case.  But team members do reserve the right to adjust, update, or pull an extension when the need arises.

There were 30 extensions, new or updated, posted yesterday and there are 5 more waiting on me as I just roll out of bed.  It is great to see that kind of progress in the repo, please keep it coming.  But as I don't have time to play email tag among extension makers regarding this issue, I have to trust that this guideline is being followed.  If you are an extension maker and you see one of your extensions updated without your being consulted and it is a concern to you, either contact the person who submitted the update or bring it up in the extension's TCE News thread.  

Many hands make for light work, but communication is also vital in the process.

And most of all thanks everyone for your time and efforts.

« Last Edit: March 07, 2010, 08:46:20 PM by Jason W »

Offline xtrdry

  • WikiUser
  • *
  • Posts: 8
Re: Extension maintainership
« Reply #1 on: March 07, 2011, 02:36:00 PM »
oh yes you are right!!

Offline JustinCB

  • WikiUser
  • *
  • Posts: 17
Re: Extension maintainership
« Reply #2 on: October 03, 2017, 08:47:28 AM »
By the way, in a batch of extensions, I sent in an updated version of python-setuptools.tcz as it was very outdated(hasn't been updated since December 2012), and packages I was building needed a newer version. Hope I'm not stepping on anyone's toes, I just thought the maintainer, which is remus, might have forgot about it, and it might be useful to have a newer version.

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5498
Re: Extension maintainership
« Reply #3 on: October 03, 2017, 09:25:46 AM »
Hi JustinCB
It is customary to first send a PM to the extension maintainer to ask their permission. If they don't reply in a week, post that you
will be updating that extension. As a courtesy, send  remus  a PM to let him know it was updated.

Offline Lukasz032

  • WikiUser
  • *
  • Posts: 8
  • Developing servers (:
    • Lukasz032 Webserver
Re: Extension maintainership
« Reply #4 on: October 24, 2017, 07:39:20 AM »
What about situations, when the author doesn't have account on forum (so there's no possibility to contact him)?
(Submitted openssl updates some days ago for 6.*/7.* branch because it was very outdated.)
Tiny-Core Extensions Maker (mainly for server use, but not only) :)

SP5LC @ KO02MD on HF/VHF

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5498
Re: Extension maintainership
« Reply #5 on: October 24, 2017, 07:58:57 AM »
Hi Lukasz032
It's not the author of the software, but the  extension-by  field listed in the info file:
Code: [Select]
Title:          openssl-1.0.0.tcz
Description:    The Open Source toolkit for SSL/TLS
Version:        1.0.0k
Author:         OpenSSL Project
Original-site:  http://www.openssl.org
Copying-policy: OpenSSL license
Size: 1.5M
Extension_by:   Jason W, bmarkus
Tags:           CRYPTO CLI LIBRARY
Comments:       Binaries only

Offline Lukasz032

  • WikiUser
  • *
  • Posts: 8
  • Developing servers (:
    • Lukasz032 Webserver
Re: Extension maintainership
« Reply #6 on: October 25, 2017, 02:03:07 PM »
Yes, I know :) You attached an .info from 5.* (which is waaaaaay more outdated, by the way).
For 6.* and 7.* the .tcz author is gordons64, whose account does not exist here.
Tiny-Core Extensions Maker (mainly for server use, but not only) :)

SP5LC @ KO02MD on HF/VHF

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5498
Re: Extension maintainership
« Reply #7 on: October 25, 2017, 04:02:41 PM »
Hi Lukasz032
OK, I think he deleted his account. In that case you can submit an update.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2544
Re: Extension maintainership
« Reply #8 on: October 25, 2017, 04:22:29 PM »
Yes, I know :) You attached an .info from 5.* (which is waaaaaay more outdated, by the way).
For 6.* and 7.* the .tcz author is gordons64, whose account does not exist here.
Hi Lukaz032   the point is the author is "OpenSSL Project"  not Gordon64.   
Also it is the Extension Maintainer who is owed the customary request to update his or her extension.  Maybe it was a typo but IMO the last person to update an extension shouldn't remove previous and/or original extension maintainers even if they changed the extension name slightly, as we loose history for one reason...   

I'm sure we are all grateful for your efforts, thanks

 
 

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 6912
    • My Community Forum
Re: Extension maintainership
« Reply #9 on: October 25, 2017, 09:15:28 PM »
It is not mentioned to which version of openssl will be updated. Be careful not to break other packages with incompatible updates.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."