Hello, I more than welcome the new book; I wanted to create a CM for the Matrix protocol, but I failed miserably due to lack of docs and tutorials. Onthe wiki: how about moving to GitHub Pages? It is not a wiki per se, but may be better on the long run: it resides in a Git repository, so it can be object to code review. Best, Gergely <div class="gmail_quote"><div dir="ltr">On Sun, Oct 30, 2016, 18:43 George Kiagiadakis <<a href="mailto:gkiagia@tolabaki.gr">gkiagia@tolabaki.gr</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all, There was a discussion on IRC on Friday about our short-term plans. I will summarize it here for the archive and for anyone else who is interested in project news. Telepathy 1.0 ============= After some discussion with ramcq, Kaffeine suggested that we should proceed with releasing telepathy 1.0 before introducing new features, as it is easier at this point to merge the 'next' branches that were left aside a few years ago. We believe (but haven't fully checked) that all the components that we are interested in have nearly-finished 'next' branches around, including KDE-Telepathy, which is the most active client at the moment. Therefore, the point is valid, so the new plan now is to finish Telepathy 1.0 as soon as possible and then carry on with a clean spec and codebase. Moving to Github ================ Currently we, all the active contributors, work on Github clones of the telepathy repositories, since it makes the development process quite easier (among other reasons). Up to now, we used to have a "TelepathyQt" organization, which included a clone of tp-qt together with the main repositories of the Qt-based connection managers, while glib-based component repositories could also be found under my profile. As you can understand, this situation was a mess, so I proposed that we move the official upstream on a single Github organization. We all agreed, but we said to keep the freedesktop repositories as mirrors. Kaffeine therefore renamed the "TelepathyQt" organization to "TelepathyIM" ("Telepathy" was already taken) and I have already cloned there all the important repositories. The move is not complete though until we setup the mirrors properly (ideally, commits should be automatically pushed to fdo when we push to github). I will ask the admins to see what we can do about that. In any case, please ***consider <a href="https://github.com/TelepathyIM" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/TelepathyIM</a> to be upstream from now on*** Note, though, that not all repositories have been moved. I took this as an opportunity to cleanup the components and "save" only the parts that make sense. The following (dead) repositories still remain in fdo: - telepathy-python (dead; deprecated in favor of gobject-introspection) - telepathy-butterfly (dead; tp-python based cm for msn, enough said...) - telepathy-sunshine (dead; tp-python based cm) - telepathy-farsight (dead; called, telepathy-farstream now) - telepathy-origami (empty repository) - telepathy-qt-farstream (empty repository) - telepathy-qt4 (symbolic link to telepathy-qt) - telepathy-qt4-yell (dead; used to be a temp repo for Call1 stuff) - telepathy-yell (dead; same as telepathy-qt4-yell) And the following also remain in fdo, though they could be saved, but since our manpower is limited, I have kept them out for now (for less clutter): - telepathy-doc (needs a major cleanup; maybe not worth saving, I'm thinking about starting a new book based on its material) - telepathy-ring (the ofono CM - not really essential for the desktop use case; it hasn't been updated since 2011, lacks support for Call1 and has no 'next' branch... I'm not dealing with it, sorry) - telepathy-phoenix (non-essential stuff for now; maybe some day...) - telepathy-ssh-contact (also non-essential stuff for now) Regarding the development process on github, one difference with the previous situation is that we are allowed to push personal branches on the main repositories. In order to keep the branches list tidy, though, I would recommend prefixing the name of each personal branch with the username of the developer working on it, so for example a branch can be called 'gkiagia/myfixes' instead of 'myfixes'. The second difference is that we can have reviews directly on the commits, plus review requests. Misc ==== Other topics that were brought up after the github move topic were: 1) Where should we keep tickets? Right now they are also split between bugzilla and github. No decision has been made yet. Our options seem to be bugzilla, github and <a href="http://phabricator.freedesktop.org" rel="noreferrer" class="gmail_msg" target="_blank">phabricator.freedesktop.org</a>. -> github: most user friendly, very limited -> bugzilla: less user friendly, more options, some basic ones are not available though (they require admin access...); currently cluttered with old & dead stuff -> phabricator: even less user friendly (imho), but the most powerful one 2) What about a wiki? The current tp wiki is abandoned and the problem with it is that you need a freedesktop account to edit it, so it's less accessible than the repositories or the ticket tracking systems. The github wiki on the other hand is very limited and goes per repository. --- George _______________________________________________ telepathy mailing list <a href="mailto:telepathy@lists.freedesktop.org" class="gmail_msg" target="_blank">telepathy@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/telepathy" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.freedesktop.org/mailman/listinfo/telepathy</a> </blockquote></div>