linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Kent Gibson <warthog618@gmail.com>
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	linux-gpio@vger.kernel.org,
	"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@google.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	stratos-dev@op-lists.linaro.org,
	"Gerard Ryan" <g.m0n3y.2503@gmail.com>
Subject: Re: [PATCH V7 1/8] libgpiod: Add libgpiod-sys rust crate
Date: Thu, 27 Oct 2022 14:18:01 +0200	[thread overview]
Message-ID: <CAMRc=Mc_f2=Qhok3b3FCcu3Hsu4pYhGVo4upow7LtCf-dNRXdg@mail.gmail.com> (raw)
In-Reply-To: <Y0/nNRu0OOXXfq/h@sol>

On Wed, Oct 19, 2022 at 2:02 PM Kent Gibson <warthog618@gmail.com> wrote:
>
> On Wed, Oct 19, 2022 at 04:52:51PM +0530, Viresh Kumar wrote:
> > On 19-10-22, 15:21, Kent Gibson wrote:
> > > That doesn't really work - you get a link to the files in github, not
> > > as a web site.  You need somewhere that will host those generated files
> > > as a web site.  You could do that with github-pages if you don't have other
> > > options.
> >
> > I don't have other options for now, so it is github.
> >
> > > When I've done that I would commit the docs to a separate
> > > branch, just for the docs, and have github-pages host that branch.
> >
> > Okay.
> >
> > > If you eventually publish your crate to crates.io you get documentation on
> > > docs.rs for free - and you can skip the documentation key in that case too
> > > - it defaults to the appropriate page on docs.rs.
> >
> > Right, that I knew.
> >
> > > I assume that would be the case long term - you just need to find
> > > someway to host them in the meantime.
> >
> > I wonder if we should be doing this at all right now, or if required
> > only Bartosz should do it instead of me, once this is merged ?
> >
>
> I was assuming it was an interim solution, so it doesn't matter so much.
>
> I'd be happy with docs.rs once libgpiod v2 is released and the bindings
> published to crates.io, and I'm personally good with looking at the
> generated docs locally in the meantime.
>
> It would be easier for others to take a look if the docs were hosted,
> but I don't have any feel as to whether that is worth the effort or not.
>
> > Maybe we need a libgpiod username for that on github ? To make it
> > independent of personal usernames ? From what I saw, the website name
> > will be username.github.io eventually.
> >
>
> A libgpiod group account might be useful.
>
> And it would be nice to have a libgpiod space somewhere, not just
> piggybacking on the gpio mailing list.  Not sure if github is the best
> place - but I haven't given it much thought.
>
> Bart, do you have any opinions?
>

For a long time I tried avoiding github etc. but I think I'll finally
have to give in and at least set up a git mirror and a discussion
place. Not sure which one is better, github, gitlab, something else?

BTW about crates.io - the python bindings in libgpiod v2 use setup.py
and I also plan to publish a python package on pypi so
decentralization is happening this time.

I also plan to split the yocto recipe into libgpiod and python3-libgpiod.

Bart

  parent reply	other threads:[~2022-10-27 12:18 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 10:47 [PATCH V7 0/8] libgpiod: Add Rust bindings Viresh Kumar
2022-10-14 10:47 ` [PATCH V7 1/8] libgpiod: Add libgpiod-sys rust crate Viresh Kumar
2022-10-17 12:59   ` Kent Gibson
2022-10-18 11:22     ` Viresh Kumar
2022-10-18 11:42       ` Miguel Ojeda
2022-10-18 11:49       ` Kent Gibson
2022-10-19  6:46         ` Viresh Kumar
2022-10-19  7:21           ` Kent Gibson
2022-10-19 11:22             ` Viresh Kumar
2022-10-19 12:01               ` Kent Gibson
2022-10-20  5:34                 ` Viresh Kumar
2022-10-27 12:18                 ` Bartosz Golaszewski [this message]
2022-10-14 10:47 ` [PATCH V7 2/8] libgpiod-sys: Add pre generated rust bindings Viresh Kumar
2022-10-14 10:47 ` [PATCH V7 3/8] libgpiod: Add rust wrapper crate Viresh Kumar
2022-10-17 12:59   ` Kent Gibson
2022-10-21 11:22     ` Viresh Kumar
2022-10-21 12:39       ` Kent Gibson
2022-10-27 12:09         ` Bartosz Golaszewski
2022-10-31 12:33           ` Kent Gibson
2022-10-31 12:45             ` Bartosz Golaszewski
2022-11-02  4:00             ` Viresh Kumar
2022-11-02 12:47               ` Bartosz Golaszewski
2022-11-02 13:08                 ` Kent Gibson
2022-11-02 16:34                   ` Bartosz Golaszewski
2022-11-03  0:38                     ` Kent Gibson
2022-11-03  8:35                       ` Bartosz Golaszewski
2022-11-03 12:29                         ` Kent Gibson
2022-11-04 15:51                           ` Bartosz Golaszewski
2022-10-18  3:27   ` Kent Gibson
2022-10-21 11:25     ` Viresh Kumar
2022-10-14 10:47 ` [PATCH V7 4/8] libgpiod: Add rust examples Viresh Kumar
2022-10-17 13:00   ` Kent Gibson
2022-10-14 10:47 ` [PATCH V7 5/8] libgpiod: Add gpiosim rust crate Viresh Kumar
2022-10-17 13:00   ` Kent Gibson
2022-10-21  9:56     ` Viresh Kumar
2022-10-14 10:47 ` [PATCH V7 6/8] gpiosim: Add pre generated rust bindings Viresh Kumar
2022-10-14 10:47 ` [PATCH V7 7/8] libgpiod: Add rust tests Viresh Kumar
2022-10-17 13:00   ` Kent Gibson
2022-10-17 14:30     ` Kent Gibson
2022-10-20 10:37     ` Viresh Kumar
2022-10-20 11:02       ` Kent Gibson
2022-10-20 12:40         ` Bartosz Golaszewski
2022-10-20 15:16           ` Miguel Ojeda
2022-10-14 10:47 ` [PATCH V7 8/8] libgpiod: Integrate building of rust bindings with make Viresh Kumar
2022-10-14 17:03 ` [PATCH V7 0/8] libgpiod: Add Rust bindings Miguel Ojeda
2022-10-20 13:29   ` Björn Roy Baron
2022-10-21  9:39     ` Viresh Kumar
2022-10-21 14:34       ` Björn Roy Baron
2022-10-25  6:42         ` Viresh Kumar
2022-10-29 17:46           ` Björn Roy Baron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMRc=Mc_f2=Qhok3b3FCcu3Hsu4pYhGVo4upow7LtCf-dNRXdg@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=alex.bennee@linaro.org \
    --cc=g.m0n3y.2503@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=stratos-dev@op-lists.linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=warthog618@gmail.com \
    --cc=wedsonaf@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).