URL: <http://savannah.gnu.org/task/?13179>
Summary: Submission of GNU libdbh Project: Savannah Administration Submitted by: edscott_wilson Submitted on: Fri 11 Apr 2014 03:37:50 PM GMT Should Start On: Fri 11 Apr 2014 12:00:00 AM GMT Should be Finished on: Mon 21 Apr 2014 12:00:00 AM GMT Category: Project Approval Priority: 5 - Normal Status: None Privacy: Public Percent Complete: 0% Assigned to: None Open/Closed: Open Discussion Lock: Any Effort: 0.00 _______________________________________________________ Details: A new project has been registered at Savannah This project account will remain inactive until a site admin approves or discards the registration. = Registration Administration = While this item will be useful to track the registration process, *approving or discarding the registration must be done using the specific Group Administration <https://savannah.gnu.org/siteadmin/groupedit.php?group_id=11285> page*, accessible only to site administrators, effectively *logged as site administrators* (superuser): * Group Administration <https://savannah.gnu.org/siteadmin/groupedit.php?group_id=11285> = Registration Details = * Name: *GNU libdbh* * System Name: *libdbh* * Type: Official GNU software * License: GNU General Public License v3 or later ---- ==== Description: ==== Library to create and manage 64-bit disk based hash tables residing on disk. Associations are made between keys and values so that for a given a key the value can be found and loaded into memory quickly. Being disk based allows for large and persistent hashes. 64 bit support allows for hashtables with sizes over 4 Gigabytes on 32 bit systems. Quantified key generation allows for minimum access time on balanced multidimensional trees. source language: C-99. ==== Other Software Required: ==== build dependencies: GNU autotools libraries: standard C libraries ==== Other Comments: ==== I hereby dub libdbh a GNU package with you as its maintainer. Please don't forget to mention prominently in the README file and other suitable documentation places that it is a GNU program. Being a package maintainer is a relationship between you personally and the GNU Project. The maintainer or maintainers are the ones who take the overall responsibility for the work done on the package. If you recruit others to contribute to the package (and some packages have hundreds of contributors), they work under your supervision. The GNU Project will sometimes need to talk with you, sometimes privately, so please make sure we know a personal email address which you read frequently. We normally publish these email addresses in the Free Software Directory. We would also like to know other ways to get in touch with you if email fails; we do not give them out. If you ever want to step down as maintainer, or would like someone else to replace you, please talk with k...@gnu.org and r...@gnu.org about it. When a package has no maintainer, we need to know about the problem so we can look for a new one. Likewise, if you think someone else should join you as co-maintainer or take over from you as maintainer, please talk with us, since we will need to establish a relationship with that person. The GNU maintainer information in http://www.gnu.org/prep/maintain/ describes a lot of procedures for GNU maintainers. It also describes who you can ask for various kinds of support or advice. If you encounter a situation where it isn't clear what to do, you can also ask ment...@gnu.org, which is a list of a few other GNU maintainers who have offered to answer questions for new maintainers. We will add you to the gnu-prog mailing list, a moderated list for announcements to GNU maintainers. We will also add you to the gnu-prog-discuss list, which can be used for discussion among GNU maintainers, but whether to stay on the list is up to you. Please send a note to gnu-prog now with a brief description of your package, so that other GNU developers will learn about it. We strongly recommend using ftp.gnu.org to make distributions available. Please see the GNU maintainers guide for the procedure, http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html. When that is set up, you'll be able to do uploads yourself. If you want to also distribute the package from a site of your own, that is fine. To use some other site instead of ftp.gnu.org is acceptable, provided it allows connections from anyone anywhere. Please write some useful web pages about the program, to put in http://www.gnu.org/software/PROGNAME. These pages should be the main web site for the program, and they should really have the information for users, not just a link to another site; please use http://www.gnu.org/software/PROGNAME whenever you give out the URL for the home page of the program. Please don't set up a "site for the program" anywhere else--if you want to do work on additional web pages about the program, please put them on www.gnu.org. (It is ok to put pages that address developers-only topics on another site, and likewise for pages that access databases.) In writing the web pages, please follow the style guidelines in http://www.gnu.org/server/fsf-html-style-sheet.html. See also http://www.gnu.org/prep/maintain/html_node/Web-Pages.html. We ask that you register your package on Savannah, at least to maintain your package's web pages. This is independent of where the actual program sources are hosted (although we encourage you to use Savannah for that too). This makes it easy to update the web pages, since you will have access to a CVS repository for the web pages and can update it as you like. Using Savannah will help the GNU Project in other ways, too. To set this up, visit http://savannah.gnu.org/. If your package was already being developed on Savannah as nongnu, email savannah-help-pub...@gnu.org and ask them to mark it there as a GNU package. This should happen without your intervention, but feel free to ask them if a day or two has gone by without the change being made. Please also write an entry or a change for the page http://www.gnu.org/people/people.html, and mail that to webmast...@gnu.org. Note that we don't want to talk about proprietary software, so if you have worked on any, please don't mention it here. Your entry can include a link to your home page provided it fits our usual criteria for what we link to. Plesae create an entry for your program in directory.fsf.org. It will then be reviewed by (one of) the directory admin(s). Please update the package's entry when they release software updates. See http://www.gnu.org/help/directory.html#adding-entries for help. Mailing lists: please see http://www.gnu.org/prep/maintain/html_node/Mail.html for the details of creating mailing lists. Every GNU package should have at least one, bug-progn...@gnu.org, for reporting bugs. Some GNU programs with many users have another mailing list, help-progn...@gnu.org, for people to ask other users for help. If your program has many users, you should create such a list for it. For a fairly new program, which doesn't have a large user base yet, it is better not to bother with this. Please mail an announcement to info-...@gnu.org about the existence of the program, either when the program is released, or now if the program is already released. Include a brief description of the program so people can tell whether they are interested in using it. The announcement should mention the web pages on www.gnu.org and say where to get releases, normally ftp.gnu.org. Once your program is released, you should make announcements of new releases. Please send them to info-...@gnu.org; you can also send them to a special list info-progn...@gnu.org for your program if you think that is warranted. (These lists should be moderated.) Please also mention release announcements in the news feed of the savannah project site, <http://savannah.gnu.org/projects/PROGNAME>. The news feeds from the GNU project are aggregated at <http://planet.gnu.org/>. For more details about writing and publicizing announcements, please see http://www.gnu.org/prep/maintain/html_node/Announcements.html. For details on all policies and recommendations for GNU packages, please see the GNU maintainers information, at http://www.gnu.org/prep/maintain/, and GNU coding standards, at http://www.gnu.org/prep/standards/. new-gnu people, could you please enter Edscott Wilson in gnuorg/maintainers and add him to the gnu-prog lists? Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org www.gnu.org Skype: No way! That's nonfree (freedom-denying) software. Use Ekiga or an ordinary phone call. ==== Tarball URL: ==== https://sourceforge.net/projects/dbh/files/dbh/ _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/task/?13179> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/