-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promoting xournalpp #2045
Comments
Hi Matthias All your ideas sound pretty good to me. Let me add some more ideas:
Best wishes, |
In my opinion, the top priority is getting an official website up (e.g. |
Yes, visibility is a problem, I was looking for an app to easily make notes on my PDF-s since several months and I couldn't find anything else than Foxit Reader (which is not very good on linux) and I have found it two days ago accidentally. Moreover I couldn't find any comparison of xournal and xournal++ (It would be nice to have it described in README, which would be more readable with table of contents), currently I just assume xournal++ is alive fork of dead xournal.
I think for now simple docsify site would be enough for basic instructions and informations. |
This is a good point--we'll have to keep this in mind when we make the website.
There's a Debian maintainer in the community working on this, but I don't know what the current status is. But we definitely need improvement here...it's just that it's hard to get around to doing given our limited time and resources.
I'm personally of the opinion that simple websites, like documentation sites, should only use pure HTML/CSS. We've been considering setting up a very simple website based on https://www.mkdocs.org/ or https://readthedocs.org/. Should be trivial with GitHub pages and GitHub actions. |
I created a draft Wikipedia page and added Xournalpp to Comparison of note-taking software.
From what I have read it's a rather long process to get into the Debian repo. |
Good job with the wiki page @matzebond! One minor thing: infinity pages are not yet implemented. So you may want to delete the phrase "and infinity mode" from the wiki page. |
@matzebond You could get inspiration from LibreOffice Wikipedia page |
I removed "and infinity mode" but hopefully I can add it again soon :-) |
It takes longer than I expected. ⏳ |
On the one hand maybe Jekyll (https://jekyllrb.com/) is a good solution for this purposes. On the other hand, if you only want a website with just docs, Sphinx (https://www.sphinx-doc.org/en/master/) would be a good choice. Both solutions will be generate a website out of pure markdown files. |
Thanks for your suggestions @daholzfeind. |
@rolandlo Maybe I can help, creating the website. Should I open a Follow Up Issue/PR? |
@daholzfeind |
@daholzfeind @rolandlo Edit: to elaborate on why I went with MkDocs: I don't like the rst syntax, and Sphinx is very complex and difficult to set up properly. Jekyll is not as convenient to install (requires Ruby, which people would have to go out of their way to install). MkDocs only needs Python (available on many computers), and it also includes a nice search feature out-of-the-box, which would be great for the user guide. It also uses Markdown, making it very easy for non-technical people to contribute documentation. |
@matzebond The OMG article and a review in the Linux User magazine (in German) are already included on the wikipedia draft page. Two more independent references would be: this Ubuntuhandbook post (in English) and this Linux Bibel review (in German). |
It would be good to add Xournal++ to sourceforge.net and edit site of original Xournal, which is still quite popular there (about 11.000 downloads in April). |
With some help of the community the Wikipedia article was improved and submitted again. I think we still might not have enough "secondary" sources but lets see. |
Ok, let's see if the improved article is accepted. It definitively looks quite a bit more professional now. |
@matzebond |
@matzebond |
@matzebond |
@matzebond what you can do now (even if you are newcomer)
Checklist with things to do (with checkboxes- things which can be easily marked as "done" ):
Other ideas:
It would be nice to add link (where such al link exists) to every of these points (it would make it easier to navigate and check progress) |
I think, that adding xournalpp to Debian repositories should have it's own issue, so I have created it. #2148 |
@matzebond You have probably noticed that the wikipedia article has been rejected again (3 months ago). The reviewer comments:
I don't quite get what they expect. Let me mention nevertheless, that the well known |
@rolandlo |
What about trying the German version then? Seems like they have a bit lower requirements. There is already an article about Xournal (without any references except the user manual and the website of Xournal++) |
Sound like a good idea. I will look into creating a draft for the German
Wikipedia and hopefully this will also make acceptance of the English
version more likely.
Roland Lötscher <[email protected]> writes:
… What about trying the German version then? Seems like they have a bit lower requirements. There is already an article about Xournal (without any references except the user manual and the website of Xournal++)
|
By the way I think we should call our application |
I've whipped the Debian packaging into shape, see https://bugs.debian.org/956272 and branch Pull requests against |
@barak Thank you for your efforts. I think the list of Xournal++ team members should include my name (and Email address [email protected]), since it is included in the About dialog for version 1.0.20 (to which I have contributed). |
@rolandlo Thanks, that's fantastic. I was unaware of #2148, would have commented there if I'd known. Will shift this discussion over. I've already uploaded to Debian (freeze is already underway, so in a bit of a rush to slip it in) so these debian/copyright fixes will go into the next upload. As a general comment, because the file isn't functional, transcription errors etc can easily slip in. Especially if it's me doing the editing based on my rushed interpretation of comments by other people. Pull requests or patches or whatever avoid this... |
I have translated the Wikipedia article for the german Wiki. There is no draft process but they still want some changes ("Wikifizieren") otherwise the article might get deleted. There is now also an entry in Wikidata so at some point it should be enough evidence for accepting into the english Wiki. |
As for sources meeting Wikipedia's notability criteria, I learned about this project from a German Linux magazine. When I find the real thing and not a stripped down online version (which sadly does not contain the article of interest), I can provide more info, perhaps even a scan of the article. |
@sven-frotscher Isn't this the same as this article, which is already referenced on the Wikipedia page? |
@rolandlo You're right, my bad. |
The German wiki page on Xournal++ is a bit outdated, since it claims that 1.0.18 is the latest version. Would someone be willing to update it to the newly released version 1.1.0 / 1.1.0-hotfix-1? |
Done :) |
Thanks @matzebond |
@rolandlo could you please specify the copyright (ideally CC BY-SA 4.0) of https://github.com/xournalpp/xournalpp-examples then I can import the images to wikimedia. |
@matzebond I have added the CC-BY-SA-4.0 license to the |
Thanks. The german wikipedia page now shows the new logo and picture. Btw the english wiki draft page got deleted because it was stale for 6 months. We could request an undeletion but I am currently not interested in improving and re-resubmitting it. |
|
@matzebond there is also an article on it.wikipedia. |
In this issue we collect some ideas for generating publicity and growing the userbase of xournalpp.
what you can do now (even if you are newcomer):
if you have a little but more energy:
current status: a draft is in limbodraft got deleted due to inactivitygot removed from the comparison page because of draft statusOther ideas:
The text was updated successfully, but these errors were encountered: