Re: [Savannah-hackers-public] Pusing to Git repo declined
On 26.05.2016 22:50, Paul Smith wrote: On Thu, 2016-05-26 at 13:41 -0700, Jim Meyering wrote: On Tue, May 24, 2016 at 10:30 PM, Aljosha Papsch wrote: Thanks for the clarification. I will fix these files now. While forcing users to push clean files is unexpected for user, I guess it would be great if these messages were warnings and would not result in a fatal error. Users could then decide for themselves whether to clean up files, in the sense "You have been warned". Is that possible? The problem with this is that it's not possible in Git to "change" a commit once it's been made, except by "rewriting history", and once a commit is pushed to a public server it's typically a very bad idea to rewrite its history. So, if you simply warn about these problems but let the commit push succeed, then there is no way for the user to clean up the mess except by adding a new commit on top which undoes the problems. It is really unpleasant, in the project history, to see a constant set of "push a change, push a cleanup to the change" commits. If the project is serious about enforcing these habits then the right way to do it is by rejecting commits that don't meet the criteria, so that the user can fix them and avoid incorrect commits appearing in the repository in the first place. How do you fix the commit locally? Is it alright rewriting history that's not been pushed yet?
Re: [Savannah-hackers-public] Pusing to Git repo declined
On 25.05.2016 05:27, Bob Proulx wrote: Assaf Gordon wrote: Hello Aljosha, Aljosha Papsch wrote: today I tried pushing to a Git repository via SSH, but it fails: ... remote: error: hook declined to update refs/heads/master ... Why does Savannah reject my changes? If it's really about coding style, as the messages suggest, I will be happy fixing those. But I can't believe Savannah is trying to make me push clean files :) Is there some other issue? Let me check that and hopefully I'll have an answer soon. Honestly I when I set up that repository I simply cloned the coreutils setup. It has that configuration. Sometimes the cut-n-paste paradigm can catch up with you. That is the case here and how I did it. However I personally would consider it. Most of the issues it was complaining about look like real issues to me. It was complaining about spaces before TABs. That is almost always a bad thing. It complains if the file doesn't end with a newline. Not ending with a newline causes the file to be treated as a binary file instead of a text file since by definition text files are lines terminated by newlines. Things like that are actually very important errors. The trailing whitespace is a much lessor issue but tends to be a problem for gratuitious diffs between different committers. I have removed that hook from the git repository. You won't get that rejection from it for any content now. Sorry for the unpleasant interaction from my cloning another setup for you. Bob Thanks for the clarification. I will fix these files now. While forcing users to push clean files is unexpected for user, I guess it would be great if these messages were warnings and would not result in a fatal error. Users could then decide for themselves whether to clean up files, in the sense "You have been warned". Is that possible? Aljosha
[Savannah-hackers-public] Pusing to Git repo declined
Hi,
today I tried pushing to a Git repository via SSH, but it fails:
$ git push origin master
Counting objects: 51, Fertig.
Delta compression using up to 4 threads.
Compressing objects: 100% (48/48), Fertig.
Writing objects: 100% (51/51), 26.93 KiB | 0 bytes/s, done.
Total 51 (delta 34), reused 2 (delta 1)
remote: src/error.c:48: trailing whitespace.
remote: + for (j = 0; j < ne->num_input; j++)
remote: src/feedforward.c:63: space before tab in indent.
remote: + tmp +=
pow(ne->connection[i]->output,j)*binom(i,j)*binom((i+j-1)/2,j);
remote: src/load.c:46: trailing whitespace.
remote: +
remote: src/load.c:61: trailing whitespace.
remote: + ne->connection[j] = >neurons[(int)(tmp)];
remote: src/msmco.c:85: trailing whitespace.
remote: + for (j = 0; j < nn->neurons[i].num_input; ++j, ++k)
remote: src/network.c:119: space before tab in indent.
remote: +/* free the previous array if any */
remote: src/network.c:173: space before tab in indent.
remote: + /* do nothing */
remote: src/network.c:174: space before tab in indent.
remote: + return 0;
remote: src/network.c:177: space before tab in indent.
remote: + free(ne->connection);
remote: src/network.c:306: space before tab in indent.
remote: + network_print(nn);
remote: src/parser.c:616: trailing whitespace.
remote: +
remote: src/parser.c:623: space before tab in indent.
remote: + printf("OUTPUT FILE NAME = %s [OK]\n",
config->output_file_name);
remote: src/parser.c:624: space before tab in indent.
remote: + break;
remote: src/parser.c:637: space before tab in indent.
remote: + break;
remote: src/parser.c:672: space before tab in indent.
remote: + };
remote: src/save.c:133: new blank line at EOF.
remote: tests/invert_order.input:118: new blank line at EOF.
remote: error: hook declined to update refs/heads/master
To alip2...@git.sv.gnu.org:/srv/git/gneuralnetwork.git
! [remote rejected] master -> master (hook declined)
error: Error while sending some references to
'alip2...@git.sv.gnu.org:/srv/git/gneuralnetwork.git'
Git ignores LC_ALL, so the messages from local Git are translated by me.
Why does Savannah reject my changes? If it's really about coding style,
as the messages suggest, I will be happy fixing those. But I can't believe
Savannah is trying to make me push clean files :) Is there some other issue?
Best regards
Aljosha
Re: [Savannah-hackers-public] Submission of Wine programs
Hi Savannah hackers, Am So, 27. Sep, 2015 um 12:15 schrieb Karl Berry <k...@freefriends.org>: What's the policy about accepting programs that run on Wine? I'm asking this because of the submission: https://savannah.gnu.org/task/index.php?13750 I don't recall the question being explicitly asked before. It seems to me that even if a program runs under Wine, in practice a package that works only in a Windows environment of whatever kind will necessarily induce people to use Windows -- thinking that people will go install wine just to run such a package seems delusionary to me. Therefore I conclude the submission should not be accepted. We have certainly rejected Windows-only submissions in the past. That's my opinion. If you want to get an official ruling, gnu-advis...@gnu.org is the place to ask. --karl Another compelling reason to reject Windows/Wine only software is that building those packages is unreasonably hard or even impossible with free software. One example is HeidiSQL. It is released as free software, with a big source code button on the download page[0]. Though, when I download it I only find build information files for some proprietary build program. This indicates that GNU/Linux "support" via Wine (as mentioned on the download page) is only an afterthought. Best regards, Aljosha Papsch [0] http://www.heidisql.com/download.php
Re: [Savannah-hackers-public] ikiwiki update on commit
Am Dienstag, den 01.10.2013, 16:44 + schrieb Karl Berry: Hi Aljoscha and all, I (finally) installed your local.css for http://savannah.gnu.org/maintenance with the tweaks we talked about. It wouldn't be my personal style, but if it makes other people happy, fine by me. karl Well, I'm certainly happy! :) Best regards. -- GPG: 4F20BC96 http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] ikiwiki update on commit
Am Sonntag, den 08.09.2013, 22:53 + schrieb Karl Berry:
You're right. Well, it still seems wrong to me to specify
background-color without foreground color, but since we haven't received
complaints about it, I guess no one uses white on black any more. In
any event, this doesn't need to be different than Savannah.css. For
that matter, I wonder if we could just use Savannah.css.
If we were to use Savannah.css we would gain a big overhead of rules,
while not getting rid of local.css since we still want to (I guess)
apply some rules to ikiwiki specific stuff.
Additionally, I don't see Savannah.css changing regularly or at all, so
imo it won't hurt having a seperate CSS file.
Other comments:
font-family: sans-serif;
Why? If someone prefers serif fonts, I see no reason to override their
choice.
Savannah.css uses arial,helvetica, which are sans-serif fonts.
Therefore, we should also use a sans-serif font in local.css, for
consistency reasons. sans-serif (the CSS value) is a compromise
between consistency and user choice (the user might still want to use
another sans-serif font).
h1 {
border-bottom: 2px solid black;
}
Not sure what we're gaining by underlining titles (at least I'm
supposing that is the effect).
I took this from various Savannah sites, where the main header is
underlined, to mark it visually as the main header. For example:
https://savannah.gnu.org/my/groups.php
https://savannah.gnu.org/my/
... and others
For the underline to be visually correct, only one h1 tag should be used
on a wiki page (I saw multiple on the front wiki page).
blockquote {
font-style: italic;
}
I know this was done sometimes in other css's for quoting email, but I
think writing lots of text in italic is just wrong.
How about a left border then, like some MUAs do it?
Besides, blockquote is used for a variety of things.
This is a semantic mistake, and should be avoided, imho. If we are
going to keep the mistake, the blockquote CSS rule should be removed.
pre {
background-color: #fffca8;
I know the old wiki printed code blocks on a colored background, but it
always seemed ugly and pointless to me.
I would keep a slight tone (maybe #dd). This way, when skimming a
page, you better memorize where the code blocks are (imo). So when
coming back to the page, e.g. for a forgotten command, you don't have to
start poking around the sentences, but just scroll down to the second or
so colored box.
Will await your comments before installing ...
Best,
Karl
Best regards.
--
GPG: 4F20BC96
http://rpapsch.de/gpg.asc
Global Surveillance UID: e3489cb7-0c4a-4781-b306-8381da9d0a43
signature.asc
Description: This is a digitally signed message part
Re: [Savannah-hackers-public] ikiwiki update on commit
Am Mittwoch, den 04.09.2013, 23:51 + schrieb Karl Berry: Aljoscha, when you want me to look at your css again, let me know. (I trust you got my comment about color setting.) Yes, I got the comment, but only came to it today: http://codepad.org/rLaxUqRP I added the a:active rule, which I found is the only additional rule needed. I also looked at Savannah.css and it doesn't do it differently. Best regards. -- GPG: 4F20BC96 http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] our wiki status
Am Montag, den 26.08.2013, 22:24 + schrieb Karl Berry: I'm fine with some savannah-ish style in theory, but I'd like to concentrate on getting the basic functionality working first. I'll come back to this. Thanks! BTW, stating Copyright and CC0 are mutually exclusive. The whole point of cc0 is waiving copyright. CC doesn't make it easy to find (last time I looked), but I believe the recommended text is: To the extent possible under law, Your Name has waived all copyright and related or neighboring rights to Your Program. This work is published from: Your Country. http://creativecommons.org/publicdomain/zero/1.0/ I thought the copyright line was still needed to prepare for the case when section 2 is invalidated somewhere and that section 2 overrides the copyright line (where the waiver is applicable). I guess I've been wrong. I just changed the license header, so you can come back to the file whenever you come back to it: http://codepad.org/O1A9Cc5y Best regards. -- GPG: 4F20BC96 - the public key can be found here: http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] our wiki status
Am Montag, den 26.08.2013, 00:36 + schrieb Karl Berry: As Aljoscha pointed out, ikiwiki has lots of bells and whistles. I haven't done anything along those lines. About that: I remade the little stylesheet: http://codepad.org/haLiNIHY It's not much, just a few lines of border, spacing, color settings (imo this is trivial work, but I added the copyright line nevertheless). It resembles the default Savannah style, so it would be nice to see it used (and/or improved). style.css says: /* Note that instead of modifying this style sheet, you can instead edit * local.css and use it to override or change settings in this one. */ local.css can also reside in the repository, if desired. Best regards. -- GPG: 4F20BC96 - the public key can be found here: http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] ikiwiki on savannah
Am Montag, den 19.08.2013, 08:12 -0600 schrieb Bob Proulx: Yes. There is a Debian package for ikiwiki. I haven't yet gone through a complete installation and use of ikiwiki anywhere yet though. Therefore I am still missing some knowledge myself about how ikiwiki works. Since ikiwiki is a wiki compiler it isn't quite as simple as doing an apt-get install ikiwki and having that be enough. I think if I had installed it elsewhere already then I would know the details well enough to proceed. I think that for someone knowledgeable in it that it really is as simple as installing the package and then pointing Apache to it. [...] I don't have much Debian experience. Help? I don't see ikiwiki setup being Debian specific. I just haven't installed and configured ikiwiki myself. For me I need to install it someplace in a scratch area and try it before doing it on the production Savannah. Has anyone on the list set up ikiwiki before? Can I get a tutorial? I have test servers available to play with so that we can work through the issues. Otherwise I will plan on setting up a victim test installation where folks here can play with it and then we will all learn through it together. Hi, After the little discussion a few months back, I experimented a little with ikiwiki (https://lists.gnu.org/archive/html/savannah-hackers-public/2013-03/msg00049.html): The basic setup (which involves installing the package and running ikiwiki --setup) makes four directories / files (where name is the wiki name): 1. The repository (in ~/name.git) - this needs to be moved wherever we want it (remote or not). It is the master repository, which people would want to check out. 2. The generated web pages (in ~/public_html/name) - this needs to be moved in the web server's directory. 3. A checked out repository (in ~/name) - this is needed for web editing. Basically, the frontend CGI script writes the changes in this repository, and commits and pushes it to the master repository (which in turn pings the CGI script to update the web pages). 4. name.setup - this file holds the configuration of the wiki. It needs to be kept somewhere to be able to make changes. Once a change is made, `ikiwiki --setup setupfile' needs to be run. If one of of the three directories is moved, the location needs to be changed in the setup file as well. http://ikiwiki.info/setup/#index6h2 explains changing the locations pretty well. For our case, where the master git is somewhere remote, this explains it well which config files one needs to edit: http://ikiwiki.info/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines/ Apart from moving directories around and editing the config files, we would also have to set up CGI in Apache (if it's not already done). If you don't want to move directories around, ikiwiki also has some command line options, with which you can specify the directories. Best regards.
Re: [Savannah-hackers-public] ikiwiki on savannah
Am Montag, den 19.08.2013, 08:12 -0600 schrieb Bob Proulx: [...] What I forgot to mention: ikiwiki has really good themeability! When experimenting, I cooked up a little stylesheet which resembled the style used in Savannah's tracker messages. Unfortunately, the CSS file is long gone, along with the experiments I did. But it shouldn't be too hard to write it once more. Best regards.
Re: [Savannah-hackers-public] Reviewing of project: Named Constant Generator (GenNC)
Am Donnerstag, den 15.08.2013, 18:19 +0200 schrieb Joan Lledó: Make sure to apply all changes requested, so you will only need to re-register once. The re-registration URL found in our acknowledgment of your earlier registration will direct you to the proper location where you can re-register your project. Why do you prompt him to re-register? All that's needed is that she uploads an updated tarball on the tracker. If that's what you mean with re-registration I would rephrase it. I guess you have got this from one of Rudra's reviews. I was already a little bemused back then I first read it, but now that I see it a second time I thought it would be good to throw in my thoughts. Best regards.
[Savannah-hackers-public] GPL and “All rights reserved”
Hi, there is this new submission #12640[0] which has some files which say All rights reserved among the GPL license notice. Is this problematic? Or can it be simply dismissed, as [1] suggests? Best regards. [0] https://savannah.gnu.org/task/index.php?12640 [1] http://help.lockergnome.com/linux/rights-reserved-GPL--ftopict471741.html
Re: [Savannah-hackers-public] GPL and “All rights reserved”
Am 01.06.2013 15:32, schrieb Ineiev: On 06/01/2013 01:58 PM, Aljosha Papsch wrote: [0] https://savannah.gnu.org/task/index.php?12640 says: ASIC/FPGA mining (primary use) has no such limitations. Out of curiosity: I wonder whether anything that depends on FPGA may qualify as free software system. Can you elaborate? I was under the impression that, as stated by the submitter, the ZTEX FPGA driver is free software, therefore the primary mining method can be done with free software alone. Or am I wrong? I'm not familiar with Bitcoin mining at all.
[Savannah-hackers-public] Replying on Savannah tasks via email
Hi, I noticed several times that submitters of projects tend to reply back via email instead on the task page. Maybe we should change the sentence on the bottom of the email that is send: Reply to this item at: to somthing more attention grabbing. What about: ATTENTION: Please don't reply to this message via email, but instead use the form at: -- Regards.
[Savannah-hackers-public] Converting wiki pages
Hi, since there was no reply on my other message I took action on my own and converted the CVS wiki page from HTML to Markdown: http://codepad.org/rTnE2Eb5 It worked pretty well and the converted page is displayed properly in my ikiwiki instance. All that needed to be done before invoking pandoc was to remove the header stuff (not the html head tag but the stuff at the top in the body tag up until the div class=content tag). So how about this proposal: We take the existing wiki pages, convert them and feed them into a ikiwiki instance, which would still need to be set up. The next step would be then to write more wiki pages. Best regards.
[Savannah-hackers-public] Wiki page sources
Hi, I found the program pandoc[0] which can convert text from various source languages to other languages, such as from Restructured Text to Markdown, which would ease the transition from zwiki to ikiwiki. Or in which language are Savannah's wiki pages written? Also, I would like to try converting some wiki pages but I can't find the sources. There's no edit link (understandable) but no “view source” link as well. How can I get the sources? [0] http://johnmacfarlane.net/pandoc/ I guess it's pretty well known, since it's included in many distributions.
Re: [Savannah-hackers-public] A wasteland of a wiki
k...@freefriends.org schrieb: Any thoughts on this? As I've written a half-dozen times before, I think by far the best approach is to restore the wiki to what it was before the attack. Unfortunately, I don't have the faintest idea what is involved with that or where to start. Nothing about the wiki setup ever made any sense to me. An optional but highly desirable next step IMHO would then be to rebase the wiki on ikiwiki (or similar), so that we are not dead in the water for months the next time we are cracked. Again unfortunately, though, that's just my wish, I cannot implement it. karl But if you don't know how to do the steps you explained (or to find someone who is capable) isn't the easiest and fastest step to just set up a new wiki? Of course, this would mean to start from scratch and maybe copy over from the old wiki. But I think atm it's a good solution to work with. We have to get the information back online.
Re: [Savannah-hackers-public] Test projects
k...@freefriends.org schrieb: Programming projects of any size can be accepted, regardless of their purpose, as they as follow our requirements. So I don't see a problem with exercises just because they are exercises. (BTW, as for the issue raised with the size of license text, tiny things can be licensed with a single line: /* This file is public domain (originally written by X Y, 2013). */ However, testing savannah out seems a bit different to me. I mean, sure, it can be processed in the normal way if they have code, but it all seems kind of a waste. Maybe worth seeing if they have specific questions we can answer without going to all the trouble of accepting a project? But probably they just want to play with the web interfaces. I guess there's no answer ... k Well then, let's just do it how it has been done until now. Thanks Karl and Felipe.
[Savannah-hackers-public] A wasteland of a wiki
Hi again. This time I'm writing because of the wiki on Savannah. It's been a while since the spam attack and I just thought we should fill it with some content again, especially since there are continously coming new submissions (and test projects ;-). I had to guess some things as well, for example where to upload releases. Any thoughts on this? Oh, and I have some free time the next days (and maybe weeks) so I could spend some time for writing as well.
[Savannah-hackers-public] Test projects
Hi! I am writing because there have been project submissions which the submitter only wants to use for trying Savannah out. My question is how do we treat these submissions. In the past I have approved test projects when the user uploaded some sample code to the tracker. Should we go on with this approach or do you have further thoughts about this? All the best, Aljosha
Re: [Savannah-hackers-public] source code for top command
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rahul rahul.rex@gmail.com schrieb: Gud afternoon sir, I m Rahul Shaw , I m a student of MCA department. I am looking for the source code of top command in ‘.c’ format, if u have any kind of information about that command then please send me the information. it’s my humble request to you please sir help me . here is my email-id : rahul.rex@gmail.com . I am waiting for your reply The program top is part of procps-ng. You can find the homepage here: http://gitorious.org/procps -BEGIN PGP SIGNATURE- Version: APG v1.0.8 iQE+BAEBCAAoBQJRMifIIRxBbGpvc2hhIFBhcHNjaCA8bWlzY0BycGFwc2NoLmRl PgAKCRD4/JTYsEm1oor8CADSNBqa5zfOvt5FviA4MLyxd+RKQXSiNOHQa6cHQ8MY Y1MEix5vag9I9rz2EEtl4fvhDevc+ZD+opw+O97TLvx5b6V2sjvwt6T7U+Ng2ehN Ll0IINOjn6aiHFN46GmuUruSOl/EUTF2QQuDgbrHZyIQLDv2vK4MXuYL4mTRnWsc ug7jqrK7QF8BT73ZKD8XHytWTHFurz3anLvD0CoYTBN9toooQ5YJRRqAHHrqXyWe Vy6BgMu+wy4i3eX0srqLfG39qOq78I/gYWgb48jhlpchS5PurEDCqFtN9RDbgqMn KGmsCEpMhma7KdWywKN5OTc0QyOV1nmC9YbnmmnTXZvS =diuy -END PGP SIGNATURE-
[Savannah-hackers-public] Documentation project with other source files
Hi, task #12450 [0] is a submission of a project that wants to translate “An Introduction to GCC”. For the license the submitter specified “GNU General Public License v2 or later”, although it is the GFDL. This leads me to a question: On the FDL howto page [1] it says “It is sufficient to put the full license notice in the “main” file of your document.”. Is this also true for the non-texi files in the tarball (the .po files, the example C files, …)? I know the book has been published like this before, but I want to be sure before approving it. Thanks, Aljosha [0] https://savannah.gnu.org/task/?12450 [1] https://www.gnu.org/licenses/fdl-howto
Re: [Savannah-hackers-public] proj_email.txt
k...@freefriends.org (Karl Berry) writes: Next time a project submission is approved, could you please ask the owner to send us a copy of the complete email? I'd like to see how it comes out, and make sure I didn't make a mistake editing. (If the welcome mail is copied to any mailing list, as it should be, I'm not seeing it :(.) Thanks much, Karl Here it is, from task #12443: Your project registration for Savannah has been approved. Project full name: libcasheph Project system name: libcasheph Project page:http://savannah.nongnu.org/projects/libcasheph Please note, that it will take up to half an hour for the system to be updated (CVS repository creation for instance) before your project will be fully functional. Enjoy the system, and please tell others about Savannah. Let us know if there is anything we can do to help you. -- the Savannah Volunteers Post scriptum, important note: In order to release your project, you should write copyright notices and license notices at the beginning of every source code file, and include a copy of the plain text version of the license. If your software is published under the GNU GPL license, please read http://www.gnu.org/copyleft/gpl.html.
[Savannah-hackers-public] Submission with Copyzero X license
Hi, submission #12012[0] contains material licensed under Copyzero X license[1][2]. From the little information I could find about it that is not in Italian it seems to be a license which is not necessarily free, in the same spirit of CC licenses where one can choose among several licenses. Unfortunately, the license text is in Italian. Is there anyone who knows more about it and can tell if the submitted project contains a free variant? Thanks, Aljosha [0] http://savannah.gnu.org/task/?12012 [1] http://en.wikipedia.org/wiki/Copyzero [2] http://waste.informatik.hu-berlin.de/Grassmuck/06_KNAW-Social_Contract.pdf (search for Copyzero)
[Savannah-hackers-public] Spam submissions
Hi, there are lately some project submissions from user hfur99, which seem to be more spam than serious. The project names are all very similar (freekernel, gkernel, urecursivekernelfunction, freeuarch, guarch 2 times, markovuarchalgorithm to name them), the description is the project name and tarballs are all empty. Additionally the user does not respond but keeps submitting new projects. Marvin already lost his nerves ;) How do we deal with this? Just delete the projects and close the tasks? Or wait? Best regards, Aljosha pgpTGSY4Az64S.pgp Description: PGP signature
[Savannah-hackers-public] README is missing copyright statement
Hi, I looked into submission of Contamination Pipeline (https://savannah.gnu.org/task/?11943) and all files are fine except README is missing a copyright notice. Is it fine in this case to accept the project with the message that the notice should be added asap? Regards, Aljosha signature.asc Description: This is a digitally signed message part.
[Savannah-hackers-public] Proposed review of xvidcap
Hi, I looked over xvidcap (https://savannah.gnu.org/task/index.php?11902). I oriented the reply after xenu's style of answers, if it's OK. Your tarball contains several files which lack a license header and copyright notice. These files are non-trivial files which are longer than 10 lines. To fulfil the requirements please add these informations. On http://www.gnu.org/licenses/gpl-howto.en.html you find more information regarding this subject. The files missing the license header are: ChangeLog Makefile.am README TODO.tasks configure.in all the Makefile.am files ppm2mpeg.sh doc/omf.make doc/xmldocs.make doc/man/man.make xml files in doc/xvidcap image files -- either include copyright notice in files or mention the copyright and license for the files in the README src/gnome-xvidcap.glade src/xvidcap-intl.h src/dbus-server-object.h Please resubmit your tarball once you updated these files. signature.asc Description: This is a digitally signed message part.
Re: [Savannah-hackers-public] Want to be a Volunteer
Am Dienstag, 8. Mai 2012, 10:33:09 schrieb Niladri Sekhar Roy: Hi, I am Niladri Sekhar Roy from India. I have just completed Masters in Computer Science. I didn't have much knowledge in Linux but I am learning it now. I want to contribute in open source development. So I do a gogle and found this link. I need some information - 1) What is the elegibility to become a volunteer? 2) How can I make contribution in development? Regards, Niladri First of all, Linux development is not done on Savannah - it is a place for all kind of projects, many of them part of GNU. Then GNU folks prefer to talk about free software rather than open source, why is explained on [1]. On [2] are many projects needing help. You'll find many entries, so you shouldn't get bored ;) Regards, Aljosha [1] http://www.gnu.org/philosophy/open-source-misses-the-point.en.html [2] https://savannah.gnu.org/people/ signature.asc Description: This is a digitally signed message part.
