Rmarkdown contains code without license statement - is this allowed on CRAN?

2018-01-12 Thread Andreas Tille 
Hi,

as I reported in the ITP bug for r-cran-rmarkdown[1] the original source
contains parts without licensing statement.  This conflicts with DFSG.
I wonder whether this is permitted on CRAN.  The only clue I would have
is to restrict the functionality of the package.

The r-cran-rmarkdown package is needed to package shiny-server (and
other packages) which is on my todo list.

Kind regards

Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884115#26

-- 
http://fam-tille.de

Re: Packaging shiny-server (Was: Bug#886815: ITP: r-cran-git2r -- GNU R access to Git repositories)

2018-01-12 Thread Andreas Tille 
Hi,

On Fri, Jan 12, 2018 at 10:43:55PM +0100, Philip Rinn wrote:
> On 10.01.2018 at 14:40, Andreas Tille wrote:
> > Feel free to commit any changes you consider an enhancement!
> 
> already did and the package builds now at least.

If I remember correctly the status I reached with the old version was
also "Builds - but does not install since the server does not start".
 
> > I would work down the list or r-cran-* packages step by step and than see 
> > how 
> > complicated the actual shiny-server packaging is.
> 
> As I said, I don't think there are any left (besides rmarkdown, which you are
> working on).

Yep, next target.
 
> > I vaguely remember the nodejs stuff was quite complex - specifically for me 
> > since I have no idea about all this nodejs / JS stuff at all.
> 
> Yes, there are a lot of nodejs dependencies which seem not to be packaged 
> (didn't
> check ITPs / RFPs):
> 
> node-client-sessions
> node-http-proxy
> node-morgan
> node-pause
> node-regexp-quote
> node-rewire
> node-shiny-server-client -> https://github.com/rstudio/shiny-server-client/
> node-sockjs
> node-stable
> node-unixgroups -> https://github.com/rstudio/node-unixgroups/
> 
> I have absolutely no experience in packaging this stuff :-(

Same for me. :-(

I'm somehow optimistic that these all follow a common scheme.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Re: Packaging shiny-server (Was: Bug#886815: ITP: r-cran-git2r -- GNU R access to Git repositories)

2018-01-12 Thread Andreas Tille 
Hi Philip,

On Thu, Jan 11, 2018 at 06:19:19PM +0100, Philip Rinn wrote:
> >r-cran-broom
> >r-cran-bubbles
> >r-cran-dbplyr
> >r-cran-ggvis
> >r-cran-highcharter
> >r-cran-leaflet
> >r-cran-mclust
> >r-cran-psych
> >r-cran-rlist
> >r-cran-shinysignals
> >r-cran-shinythemes
> >r-cran-wordcloud
> >r-cran-rmarkdown
> > 
> > This list possibly needs to be worked down.
> 
> are you sure?

No. :-)

I just guessed from what on the production machine that is used here is
installed.  So in any case I need to package these - may be that these
are not really stricht dependencies of shiny-server (even if
r-cran-shinysignals and r-cran-shinythemes sound really "shiny")

> grep'ing the source code for those packages ('broom', ... of course)
> only shows 'rmarkdown' occurring in the source.

I'll take this as next target.
 
Kind regards

   Andreas. 

-- 
http://fam-tille.de

Re: r-pkg-team page on wiki.d.o.

2018-01-12 Thread Charles Plessy 
Le Fri, Jan 12, 2018 at 07:17:32PM +0300, Boris Pek a écrit :
> 
> Sorry, but it looks ugly:
> https://salsa.debian.org/explore/groups?utf8=%E2%9C%93=Debian+R+Packages+Maintainers
> 
> Please add the link in the end of description.

Amended, thanks.  I also moved the group ID from the description the
wiki page.

Have a nice week-end,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Re: Re: Packaging shiny-server (Was: Bug#886815: ITP: r-cran-git2r -- GNU R access to Git repositories)

2018-01-12 Thread Philip Rinn 
On 12.012018 at 22:43:55, Phili Rinn wrote:
> Yes, there are a lot of nodejs dependencies which seem not to be packaged 
> (didn't
> check ITPs / RFPs):

missed: node-bash

Best,
Philip

Re: Packaging shiny-server (Was: Bug#886815: ITP: r-cran-git2r -- GNU R access to Git repositories)

2018-01-12 Thread Philip Rinn 
Hi,

On 10.01.2018 at 14:40, Andreas Tille wrote:
> Feel free to commit any changes you consider an enhancement!

already did and the package builds now at least.

> I would work down the list or r-cran-* packages step by step and than see how 
> complicated the actual shiny-server packaging is.

As I said, I don't think there are any left (besides rmarkdown, which you are
working on).

> I vaguely remember the nodejs stuff was quite complex - specifically for me 
> since I have no idea about all this nodejs / JS stuff at all.

Yes, there are a lot of nodejs dependencies which seem not to be packaged 
(didn't
check ITPs / RFPs):

node-client-sessions
node-http-proxy
node-morgan
node-pause
node-regexp-quote
node-rewire
node-shiny-server-client -> https://github.com/rstudio/shiny-server-client/
node-sockjs
node-stable
node-unixgroups -> https://github.com/rstudio/node-unixgroups/

I have absolutely no experience in packaging this stuff :-(

Best,

Philip

RE:How to get some replacement for a commit list

2018-01-12 Thread PICCA Frederic-Emmanuel 
> I have submitted a pull request with such a script:

>  https://salsa.debian.org/mehdi/salsa-scripts/merge_requests/2/commits

Hello,

Is it just me or...

I find that this token things is a regression from a security point of view.
I did my best to put my pgp private key on a nitrokey device. And I use the 
gpg-agent in order to deal with ssh.

So now I have no private (gpg and ssh) keys on my computers.

Now it seems that we need to put somewhere on computers the token in orde to 
use these scripts.

Is it possibble to use the gpg-agent in order to manage this salsa api 
manipulation ?

Cheers

Frédéric

Re: r-pkg-team page on wiki.d.o.

2018-01-12 Thread Boris Pek 
Hi,

>>  It could be useful to add this link in the description of the team in
>>  the salsa page.
>
> Done, thanks for the suggestion !

Sorry, but it looks ugly:
https://salsa.debian.org/explore/groups?utf8=%E2%9C%93=Debian+R+Packages+Maintainers

Please add the link in the end of description.

Also you may use two newline symbols to split strings to paragraphs
for better look of: https://salsa.debian.org/r-pkg-team

Best wishes,
Boris

Re: How to get some replacement for a commit list

2018-01-12 Thread Sébastien Villemot 
On Fri, Jan 12, 2018 at 04:55:38PM +0100, Andreas Tille wrote:

> That's *very* interesting.  I also need it for the Blends metadata
> gatherer.  This needs d/changelog, d/control, d/upstream/metadata of all
> projects of a packaging team.  If you dive into this I'd be really happy
> to get hints.  On Alioth this was easy by running a cron job on the
> machine iterating through all dirs of a team and fetching the debian/
> dir.  The Alioth -> Salsa move is breaking this (and other things for
> the Blends tools).

I have submitted a pull request with such a script:

 https://salsa.debian.org/mehdi/salsa-scripts/merge_requests/2/commits

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: How to get some replacement for a commit list

2018-01-12 Thread Boris Pek 
Hi,

>>> We are now supposed to use the email notifications from GitLab ("Emails on
>>> push" under "Settings -> Integrations").
>>
>> there is a script for this if you don't want to use the web interface (I 
>>didn't
>> test it though)
>>
>> https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh
>
> Did this worked for you?
>
>  $ emails_on_push.sh r-pkg-team ti...@debian.org
> Project r-pkg-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service
>
>  $ emails_on_push.sh science-team ti...@debian.org
> Project science-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service

Just fix the script using idea from:
https://lists.debian.org/debian-devel-games/2018/01/msg00010.html

Best wishes,
Boris

Re: How to get some replacement for a commit list

2018-01-12 Thread Andreas Tille 
Hi Sébastien,

On Fri, Jan 12, 2018 at 04:32:22PM +0100, Sébastien Villemot wrote:
> >  $ emails_on_push.sh r-pkg-team ti...@debian.org
> > Project r-pkg-team not found among your owned projects on 
> > https://salsa.debian.org/api/v4 service
> > 
> >  $ emails_on_push.sh science-team ti...@debian.org
> > Project science-team not found among your owned projects on 
> > https://salsa.debian.org/api/v4 service
> 
> Notifications have to be set up on a per-project basis, not on a group-basis.

Ahhh, I should have read more closely.
 
> I am currently writing a script to list all the projects of a group,

That's *very* interesting.  I also need it for the Blends metadata
gatherer.  This needs d/changelog, d/control, d/upstream/metadata of all
projects of a packaging team.  If you dive into this I'd be really happy
to get hints.  On Alioth this was easy by running a cron job on the
machine iterating through all dirs of a team and fetching the debian/
dir.  The Alioth -> Salsa move is breaking this (and other things for
the Blends tools).

> Also, I'm not sure it's a good model to have each of us add his personal
> address to the configuration of projects on which he/she has admin rights… The
> tracker.d.o address is really the prefered way.

Definitely.  Having personal addresses per project seems to be a really
safe way to get lots of e-mail addresses and projects forgetten in one
or the other way.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Re: How to get some replacement for a commit list

2018-01-12 Thread Sébastien Villemot 
On Fri, Jan 12, 2018 at 04:14:22PM +0100, Andreas Tille wrote:
> On Fri, Jan 12, 2018 at 03:24:53PM +0100, Philip Rinn wrote:
> > Hi,
> > 
> > > We are now supposed to use the email notifications from GitLab ("Emails on
> > > push" under "Settings -> Integrations").
> > 
> > there is a script for this if you don't want to use the web interface (I 
> > didn't
> > test it though)
> > 
> > https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh
> 
> Did this worked for you?
> 
>  $ emails_on_push.sh r-pkg-team ti...@debian.org
> Project r-pkg-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service
> 
>  $ emails_on_push.sh science-team ti...@debian.org
> Project science-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service

Notifications have to be set up on a per-project basis, not on a group-basis.

I am currently writing a script to list all the projects of a group, to
facilitate such a mass modification.

Also, I'm not sure it's a good model to have each of us add his personal
address to the configuration of projects on which he/she has admin rights… The
tracker.d.o address is really the prefered way.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: How to get some replacement for a commit list

2018-01-12 Thread Andreas Tille 
On Fri, Jan 12, 2018 at 03:49:47PM +0100, Sébastien Villemot wrote:
> > 
> > https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh
> 
> Indeed, thanks. And there is also a script for activating IRC notifications 
> (it
> would be nice to have them back on #debian-science).

No luck here as well:


$ irker.sh science-team \#debian-science
Project science-team not found among your owned projects on 
https://salsa.debian.org/api/v4 service

:-(


-- 
http://fam-tille.de

Re: How to get some replacement for a commit list

2018-01-12 Thread Andreas Tille 
On Fri, Jan 12, 2018 at 03:24:53PM +0100, Philip Rinn wrote:
> Hi,
> 
> > We are now supposed to use the email notifications from GitLab ("Emails on
> > push" under "Settings -> Integrations").
> 
> there is a script for this if you don't want to use the web interface (I 
> didn't
> test it though)
> 
> https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh

Did this worked for you?

 $ emails_on_push.sh r-pkg-team ti...@debian.org
Project r-pkg-team not found among your owned projects on 
https://salsa.debian.org/api/v4 service

 $ emails_on_push.sh science-team ti...@debian.org
Project science-team not found among your owned projects on 
https://salsa.debian.org/api/v4 service
 

:-(

Kind regards

  Andreas.


-- 
http://fam-tille.de

Re: Re: How to get some replacement for a commit list

2018-01-12 Thread Sébastien Villemot 
On Fri, Jan 12, 2018 at 03:24:53PM +0100, Philip Rinn wrote:

> > We are now supposed to use the email notifications from GitLab ("Emails on
> > push" under "Settings -> Integrations").
> 
> there is a script for this if you don't want to use the web interface (I 
> didn't
> test it though)
> 
> https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh

Indeed, thanks. And there is also a script for activating IRC notifications (it
would be nice to have them back on #debian-science).

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: Re: How to get some replacement for a commit list

2018-01-12 Thread Philip Rinn 
Hi,

> We are now supposed to use the email notifications from GitLab ("Emails on
> push" under "Settings -> Integrations").

there is a script for this if you don't want to use the web interface (I didn't
test it though)

https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh

Best,

Philip

Re: How to get some replacement for a commit list

2018-01-12 Thread Sébastien Villemot 
On Fri, Jan 12, 2018 at 02:48:38PM +0100, Andreas Tille wrote:

> since the move to Salsa there are no commits sent to a list any more
> (neither for the Debian Science nor for the packages in r-pkg-team).  Is
> there any chance to get this nice feature back?

We are now supposed to use the email notifications from GitLab ("Emails on
push" under "Settings -> Integrations").

The recommended setup is to use "dispatch+${package}_...@tracker.debian.org" as
the email address to which notifications are sent. Then people can subscribe
to those notifications through tracker.d.o (using the "vcs" keyword).

See https://wiki.debian.org/Salsa/Doc#Email_notifications

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

How to get some replacement for a commit list

2018-01-12 Thread Andreas Tille 
Hi,

since the move to Salsa there are no commits sent to a list any more
(neither for the Debian Science nor for the packages in r-pkg-team).  Is
there any chance to get this nice feature back?

Kind regards

   Andreas.

-- 
http://fam-tille.de

[RFS] mseed2sac and sac2mseed: seismic data conversion tools

2018-01-12 Thread Paride Legovini 
Dear debian-scientists,

I packaged two small utilities to convert seismic data between the two
most commonly used data formats. Both the tools use the recently
packaged libmseed2 library (thanks Pierre).

Here are the ITPs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886993
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886995

and the uploads to mentors:

https://mentors.debian.net/package/mseed2sac
https://mentors.debian.net/package/sac2mseed

I'd like to maintain these two packages in the debian-science team and
I'm looking for a sponsor.

Thank you,

Paride



signature.asc
Description: OpenPGP digital signature

Re: r-pkg-team page on wiki.d.o.

2018-01-12 Thread Charles Plessy 
Le Fri, Jan 12, 2018 at 09:23:46AM +0100, Dylan Aïssi a écrit :
> >
> > https://wiki.debian.org/Teams/r-pkg-team
> 
> It could be useful to add this link in the description of the team in
> the salsa page.

Done, thanks for the suggestion !

-- 
Charles

Re: Maintainer field value for the r-pkg-team (was Re: dh-r changes)

2018-01-12 Thread Sébastien Villemot 
On Fri, Jan 12, 2018 at 01:40:58PM +0100, Andreas Tille wrote:

> On Fri, Jan 12, 2018 at 11:22:29AM +0100, Sébastien Villemot wrote:
> > 
> > I created the r-pkg-team on tracker.d.o:
> > 
> >  https://tracker.debian.org/teams/r-pkg-team/
> > 
> > Note that since tracker.d.o does not allow multiple owners for a team, I am
> > effectively the only owner there. So don't hesitate to ask me if something
> > needs to be modified there. For the time being there is no package 
> > associated
> > to the team.
> > 
> > The good news is that Raphaël Hertzog has recently introduced a new feature 
> > in
> > tracker.d.o which allow us to put team addresses in the Maintainer field. 
> > So we
> > could decide to put:
> > 
> >  Maintainer: Debian R Packages Team 
> > 
> > in all the team's packages.
> 
> Could you add this information to the Wiki page[1].

I added a pointer to the team page on tracker.d.o (but I don't think we should
mention the Maintainer email until we have made a decision about it).

> > Then the packages will automatically appear in tracker.d.o (and other tools
> > like QA or DMD will also work).
> > 
> > By subscribing to the team on tracker.d.o, one will get the usual DAK and 
> > BTS
> > messages (there is a possibility of customizing the precise types of 
> > messages).
> 
> That means I get those e-mails that were usually sent to the science / med
> team?

Yes.

> > Note that for the moment the emails sent to 
> > team+r-pkg-t...@tracker.debian.org
> > go to /dev/null, which is not so good if some human tries to contact the 
> > team
> > at that address; but this is supposed to change in the future.
> 
> I need to admit I'll wait until this implemented since it happens that
> users try to contact the maintainer and this should be sent to real
> persons.  In other words:  The e-mail address should behave like a
> mailing list.  Speaking about this:  Will we have some kind of "archive"
> of these mails?  I'm asking with the team metrics project in mind where
> also maintainer lists were parsed ...

I don't think there is a plan for an archive of these emails, since this is not
a mailing list, only a mail alias.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: r-cran-git2r uses private header files of libgit2 (Was: Help with libgit2 needed to strip code copy from r-cran-git2r)

2018-01-12 Thread Andreas Tille 
Hi Dirk,

On Thu, Jan 11, 2018 at 10:51:45AM -0600, Dirk Eddelbuettel wrote:
> 
> I had some friendly emails with Stefan (git2r upstream) when he started the R
> package git2r (as I needed some features in my drat R package) and he
> expressed quite some frustration at working with libgit2 as it changed so
> much upstream.
> 
> I know we collectively really hate embedding copies, but r-cran-git2r may be
> defensible case because libgot2 is too complex / volatile.

Thanks for your insight, uploaded with code copy.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Re: Maintainer field value for the r-pkg-team (was Re: dh-r changes)

2018-01-12 Thread Andreas Tille 
Hi Sébastien,

On Fri, Jan 12, 2018 at 11:22:29AM +0100, Sébastien Villemot wrote:
> 
> I created the r-pkg-team on tracker.d.o:
> 
>  https://tracker.debian.org/teams/r-pkg-team/
> 
> Note that since tracker.d.o does not allow multiple owners for a team, I am
> effectively the only owner there. So don't hesitate to ask me if something
> needs to be modified there. For the time being there is no package associated
> to the team.
> 
> The good news is that Raphaël Hertzog has recently introduced a new feature in
> tracker.d.o which allow us to put team addresses in the Maintainer field. So 
> we
> could decide to put:
> 
>  Maintainer: Debian R Packages Team 
> 
> in all the team's packages.

Could you add this information to the Wiki page[1].
 
> Then the packages will automatically appear in tracker.d.o (and other tools
> like QA or DMD will also work).
> 
> By subscribing to the team on tracker.d.o, one will get the usual DAK and BTS
> messages (there is a possibility of customizing the precise types of 
> messages).

That means I get those e-mails that were usually sent to the science / med
team?

> Note that for the moment the emails sent to team+r-pkg-t...@tracker.debian.org
> go to /dev/null, which is not so good if some human tries to contact the team
> at that address; but this is supposed to change in the future.

I need to admit I'll wait until this implemented since it happens that
users try to contact the maintainer and this should be sent to real
persons.  In other words:  The e-mail address should behave like a
mailing list.  Speaking about this:  Will we have some kind of "archive"
of these mails?  I'm asking with the team metrics project in mind where
also maintainer lists were parsed ...
 
> An alternative solution for the Maintainer field would be to use the 
> (hopefully
> to be created) debia...@lists.debian.org. But this has the disadvantage that
> one will not be able to fine tune its subscriptions to DAK/BTS messages, since
> all will be sent to the list.

I also think we should have two different addresses: One for general
discussion (= debia...@lists.debian.org) and one for package maintenance
purpose.
 
> So, in short, there are two solutions for the Maintainer field:
> 
> 1) team+r-pkg-t...@tracker.debian.org
>Pros: allows fine-tuning of DAK/BTS message subscriptions
>Cons: human messages go to /dev/null (but this is temporary)
> 
> 2) debia...@lists.debian.org
>Pros: simplicity (only one email address for the team)
>Cons: address does not yet exist (but hopefully will)
> 
> I vote for 1), but I am also fine with 2) if this is preferred.

For the moment I think both are not yet usable with a very slight
preference of 1).

Kind regards

   Andreas.


[1] https://wiki.debian.org/Teams/r-pkg-team

-- 
http://fam-tille.de

Maintainer field value for the r-pkg-team (was Re: dh-r changes)

2018-01-12 Thread Sébastien Villemot 
On Tue, Jan 09, 2018 at 11:27:30AM +0100, Andreas Tille wrote:

> What we also need to clarify is the Maintainer field of r-pkg-team
> maintained packages.  I'm about to team hijack r-cran-xts[1] and for
> the moment I used
> 
>Maintainer: Debian Science Team 
> 
> 
> but we should use an own list - and one that is promising to persist the
> alioth shutdown.

I createe the r-pkg-team on tracker.d.o:

 https://tracker.debian.org/teams/r-pkg-team/

Note that since tracker.d.o does not allow multiple owners for a team, I am
effectively the only owner there. So don't hesitate to ask me if something
needs to be modified there. For the time being there is no package associated
to the team.

The good news is that Raphaël Hertzog has recently introduced a new feature in
tracker.d.o which allow us to put team addresses in the Maintainer field. So we
could decide to put:

 Maintainer: Debian R Packages Team 

in all the team's packages.

Then the packages will automatically appear in tracker.d.o (and other tools
like QA or DMD will also work).

By subscribing to the team on tracker.d.o, one will get the usual DAK and BTS
messages (there is a possibility of customizing the precise types of messages).

Note that for the moment the emails sent to team+r-pkg-t...@tracker.debian.org
go to /dev/null, which is not so good if some human tries to contact the team
at that address; but this is supposed to change in the future.

An alternative solution for the Maintainer field would be to use the (hopefully
to be created) debia...@lists.debian.org. But this has the disadvantage that
one will not be able to fine tune its subscriptions to DAK/BTS messages, since
all will be sent to the list.


So, in short, there are two solutions for the Maintainer field:

1) team+r-pkg-t...@tracker.debian.org
   Pros: allows fine-tuning of DAK/BTS message subscriptions
   Cons: human messages go to /dev/null (but this is temporary)

2) debia...@lists.debian.org
   Pros: simplicity (only one email address for the team)
   Cons: address does not yet exist (but hopefully will)

I vote for 1), but I am also fine with 2) if this is preferred.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: r-pkg-team page on wiki.d.o.

2018-01-12 Thread Dylan Aïssi 
Hi,

2018-01-10 12:59 GMT+01:00 Charles Plessy :
>
> I just drafted a r-pkg-team page on wiki.debian.org:
>
> https://wiki.debian.org/Teams/r-pkg-team
>

Thanks Charles for this.

It could be useful to add this link in the description of the team in
the salsa page. Like this someone who arrives on the salsa page of the
team can have direct access to the documentation and does not need to
search for it.
This could also be done for the science (and the future med) team salsa pages.

Sorry, I can't do it myself, I don't have enough rights.

Best,
Dylan