/dev/chat

« first day (3586 days earlier) ← previous day next day → last day (1662 days later) »

Faheem Mitha

09:35

Does anyone here own or has owned an Eco-drive? I didn't know watches could be powered by solar batteries. I guess I've been out of the loop.

3 hours later…

Faheem Mitha

12:29

I just submitted bugs.debian.org/967025

Is doing a PR on salsa (which seems to be where development repositories now live) by non-developers/maintainers a thing?

Stephen Kitt

12:40

@FaheemMitha yes, it is, and for a Python-team-maintained package there’s even a very good chance it will be merged ;-)

Faheem Mitha

@StephenKitt Would a first step be to get an account on Salsa? Or something else?

BTW, there are apparently two different Python YAML libraries, which is unfortunate.

One forked from the other some time back. So now I need to decide which one to use.

Stephen Kitt

@FaheemMitha yes, get an account, and edit the project (you can create a merge request in-browser, which is very handy for a small fix such as this one)

Faheem Mitha

People say choice is good. But choice is also sometimes annoying.

@StephenKitt I had an account on alioth once. Is that dead and gone?

Stephen Kitt

@FaheemMitha yes

Faheem Mitha

So anyone can create an account on salsa.debian.org/users/sign_in#register-pane?

Stephen Kitt

12:48

@FaheemMitha yes

Faheem Mitha

@StephenKitt Ok, thank you. And is it customary to tag the PR with the Debian bug number?

And if so, would the bug update automatically?

Stephen Kitt

@FaheemMitha yes, write your commit message as usual, and add “Closes: #NNNNNN” at the end (along with your “Signed-off-by” if you want). That will mark the bug as pending when the MR is merged, if the hooks have been set up on the project.

Don’t include the bug number in the commit title though.

Faheem Mitha

@StephenKitt The commit title would be the first line?

@StephenKitt I don't know what the Signed-off-by thing is. What is that for?

Stephen Kitt

@FaheemMitha yes; in git commit messages, the first line is the title, followed by a blank line, then the text of the commit message

Faheem Mitha

@StephenKitt Ok, noted.

Stephen Kitt

13:00

@FaheemMitha some projects require it, so many git users just include it by default (git commit -s does it for you)

Faheem Mitha

@StephenKitt Ok. Thank you.

Stephen Kitt

Developer Certificate of Origin

The Developer Certificate of Origin (DCO) was introduced in 2004 by the Linux Foundation, to enhance the submission process for software used in the Linux kernel, shortly after the SCO–Linux disputes.DCOs are often used as an alternative to a Contributor License Agreement (CLA). Instead a signed legal contract, a DCO is an affirmation that the source code being submitted originated from the developer, or that the developer has permission to submit the code. Proponents of the DCO contend that it reduces the barriers of entry introduced by a CLA. Developer Certificate of Origin Version 1.1 Copyright...

the above is what underlies “Signed-off-by” on the Linux kernel, for example

Faheem Mitha

@StephenKitt That sounds like something that primarily applies to DDs or DMs.

Presumably a circle of trust thing.

Stephen Kitt

@FaheemMitha no, for a project which requires it, it applies to all contributors

Faheem Mitha

@StephenKitt Oh.

I guess the question is whether Debian requires it.

Stephen Kitt

13:16

@FaheemMitha Debian doesn’t require it.