Re: [GNUnet-developers] anonbib
... > I am currently going through our .bib file with a newer python application. > This showed more remaining errors (This time: with the linenumber, much > faster) > and I am confident that simply using something which makes use of for example > pybtex will be easier to maintain. I decided to continue with anonbib. However I will apply fixes lint complains about and parts I complain about, so that it is easier to maintain. We might lose the ability to just merge from anonbib, but before we had git we also had our ways to merge remote code ;) The code in anonbib works, but it works just for them, their .bib file. For now I just care to make it work for out .bib which is different from theirs by content. ___ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
Re: [GNUnet-developers] Encrypted Message
Nils Gillmann transcribed 3.0K bytes: > I'm responding to the list since I see no reason why this > should be offlist. I hope this is okay for you. > > Christian Grothoff transcribed 4.4K bytes: > > > >> I will probably finish this today or tomorrow, if it builds then, we need > > >> a couple more eyes to review the content, types, URLs and so forth. > > > > > > Change of course: I took a 2nd closer look at anonbib and for now it > > > is inappropriate for the work which would have to put into it for our > > > bibtex lib. Reasons include: python2 specific issues which take too > > > long to fix. > > > > That's a very, very brief reason to give for a major change in > > direction. I don't understand at all what "python2 specific issues" > > would even be that we'd care about here. Please do elaborate _a lot_. > > > > > I have started with bibtex2html, perl based. This should give us a > > > html output in short time. I'll work on this and tell you once it is > > > usable and when you can contribute to the work on it. > > > > Eh, this makes no sense. To start with, Perl is not really a nice > > language (especially for this). We don't have anything in Perl so far! > > Also, it _does_ make sense to work with the Tor people on this one, so > > if there are issues both projects could benefit. > > > > So without further information, I'd be against this. > > > > Okay, I've slept over my last emails. > > To be fair, your argument that we don't have anything in perl and that > perl is not really a nice language is really just your opinion. > Except for styling we won't change much in the code.[1] > Anyway, back to my conclusions: > > The whole code of anonbib is in python2. It makes no use of maybe > more usable and well maintained (or: well written, more general) > bibtex modules in python. They imported their BibTeX module from > a perl module (read the code for all the reasons I mention here). > I don't see myself pushing code in their direction, because I > would have to change lots of the code base. A non-issue which > needs to be fixed nevertheless is that they have python2 > exlusively - and we are working on getting rid of python2. > > The issues with python2 in the code: > It comes down to the choice of either fixing many of our entries to > their limited BibTeX implementation (which is the main cause of > errors, we have more valid BibTeX record types), something which in > some parts can not be done with sed, or extending the python2 code. > If you haven't read the python2 code, please do. It is really not > pleasant to read in some parts. Extending will take longer than I can > justify, which leads me to: > > Last night I looked into jinja2 based bibtex->html. It is easy. As we > already use jinja2, this makes more sense than maybe eventually > sending code to freehaven's anonbib. I'll write a separate website for > this in jinaj2 and a common used bibtex module. Later we can integrate > this into the mainwebsite, but it makes sense to keep them separate. > I hope this is alright, if it isn't someone else can continue with > anonbib. > > 1: Okay, I just remembered after writing this email that we discussed >extensions to this before: we wanted some kind of search and other >features. I am currently going through our .bib file with a newer python application. This showed more remaining errors (This time: with the linenumber, much faster) and I am confident that simply using something which makes use of for example pybtex will be easier to maintain. ___ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
Re: [GNUnet-developers] Encrypted Message
I'm responding to the list since I see no reason why this should be offlist. I hope this is okay for you. Christian Grothoff transcribed 4.4K bytes: > >> I will probably finish this today or tomorrow, if it builds then, we need > >> a couple more eyes to review the content, types, URLs and so forth. > > > > Change of course: I took a 2nd closer look at anonbib and for now it > > is inappropriate for the work which would have to put into it for our > > bibtex lib. Reasons include: python2 specific issues which take too > > long to fix. > > That's a very, very brief reason to give for a major change in > direction. I don't understand at all what "python2 specific issues" > would even be that we'd care about here. Please do elaborate _a lot_. > > > I have started with bibtex2html, perl based. This should give us a > > html output in short time. I'll work on this and tell you once it is > > usable and when you can contribute to the work on it. > > Eh, this makes no sense. To start with, Perl is not really a nice > language (especially for this). We don't have anything in Perl so far! > Also, it _does_ make sense to work with the Tor people on this one, so > if there are issues both projects could benefit. > > So without further information, I'd be against this. > Okay, I've slept over my last emails. To be fair, your argument that we don't have anything in perl and that perl is not really a nice language is really just your opinion. Except for styling we won't change much in the code.[1] Anyway, back to my conclusions: The whole code of anonbib is in python2. It makes no use of maybe more usable and well maintained (or: well written, more general) bibtex modules in python. They imported their BibTeX module from a perl module (read the code for all the reasons I mention here). I don't see myself pushing code in their direction, because I would have to change lots of the code base. A non-issue which needs to be fixed nevertheless is that they have python2 exlusively - and we are working on getting rid of python2. The issues with python2 in the code: It comes down to the choice of either fixing many of our entries to their limited BibTeX implementation (which is the main cause of errors, we have more valid BibTeX record types), something which in some parts can not be done with sed, or extending the python2 code. If you haven't read the python2 code, please do. It is really not pleasant to read in some parts. Extending will take longer than I can justify, which leads me to: Last night I looked into jinja2 based bibtex->html. It is easy. As we already use jinja2, this makes more sense than maybe eventually sending code to freehaven's anonbib. I'll write a separate website for this in jinaj2 and a common used bibtex module. Later we can integrate this into the mainwebsite, but it makes sense to keep them separate. I hope this is alright, if it isn't someone else can continue with anonbib. 1: Okay, I just remembered after writing this email that we discussed extensions to this before: we wanted some kind of search and other features. ___ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
Re: [GNUnet-developers] [Help-gnunet] From IRC chat: ng0 asked me to post problems with the git docs.
On 10/06/2018 04:08 PM, Diagon wrote:> I've been back 3 times. I /really/ want to try this. I do think > this project shows a particular fragmentation of useful information, > leaving at least one reasonably competent person, even if not a > developer, throwing up their hands. Hi Diagon, Thanks for the constructive feedback. I've been trying to get people to put installation instructions into doc/documentation/chapters/installation.texi and -only- there, but despite this being easily editable by anyone involved, some developers keep throwing up instructions in all kinds of places (like the github repo Sva pointed you to, encouraging the use of non-free SaaS on top of it!). I'm not sure what to do about this, as obviously asking people to keep the documentation in one place or even just in one format is not working. Anyway, the goal is that from installation.texi we will *generate* a Web page (HTML, PDF), making the instructions easy to read even without having built the documentation. You can find a _prototype_ of the new Web page at https://stage.gnunet.org/. Once the (complex) migration is complete, we'll make 'stage' the new main site. Sadly, there is quite a bit to migrate (bug tracker, IRC logger, bibliography, continuous integration, etc.), and the only person who's recently been working on this is ng0 (thanks, ng0!). Now, to answer some of your questions: > Also, he had libcurl4-gnutls-dev. Is that a replacement for > libgnurl? Yes, if available, it can be used as an alternative. > He has no optional packages either, but included a few not > mentioned in that README: zlib1g-dev This is for compression. Very, very commonly available. > libjansson-dev This is very, very optional and new for pre66. > autopoint Very common, used somewhere in the gettext context. > miniupnpc, which of course makes me curios what these are for. Optional, for UPnP-support, a protocol to tell your NAT to open external ports. I hope this helps a bit where we are and where I hope to go! As usual, help would be welcome. Happy hacking! Christian signature.asc Description: OpenPGP digital signature ___ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
