38 ms·

Only issue is if you decide to use GitHub features like issues/prs or comments on code, those won't be transferrable I think. At least easily.

by nikivi 6y ago

Pfhreak 6y ago
Is it really though? The tools might be proprietary, but the workflow should be easy to move. E.g. You need to have a code review before a commit is merged. It happens that Github has a good set of tools for this, but if you decided that on date X you wanted to move away I don't think it would be that hard to shift away. You'd have the same mandate about code review, you just point people at a different tool set to do it.
kanox 6y ago
Email archives are even harder to transfer, and to make sense of in general. For example if you want to find the review comment thread for linux commits there is no reliable way to do it, your best bet is to google the title.
- angio 6y ago
  > Email archives are even harder to transfer, and to make sense of in general. Email archives are very easy to transfer, you simply download the mbox file from the old system and import them to the new one [0]. > For example if you want to find the review comment thread for linux commits there is no reliable way to do it, your best bet is to google the title. In my experience, projects that use a ml-based workflow have higher standards for commit messages and so the information about a commit is usually in the commit. [0] https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archi...
- Seirdy 6y ago
  > Email archives are even harder to transfer Mailing lists are trivial to distribute. Thanks to maildir and mbox, everybody has a full copy of the mailing list just as they have a full copy of the repository.
  - kanox 6y ago
    > Thanks to maildir and mbox, everybody has a full copy of the mailing list. No, that only covers emails that you personally received. You need another mechanism for older emails.
    - ddevault 6y ago
      A mechanism which is provided by mailing list archives in the form of mbox downloads. If you question the reliability of this (but apparently not the proven unreliability of GitHub), as a fallback you can just ask an older subscriber to give you their mbox.

Only issue is if you decide to use GitHub features like issues/prs or comments on code, those won't be transferrable I think. At least easily.

by nikivi 6y ago

Only issue is if you decide to use GitHub features like issues/prs or comments on code, those won't be transferrable I think. At least easily.

Pfhreak 6y ago

Is it really though? The tools might be proprietary, but the workflow should be easy to move. E.g. You need to have a code review before a commit is merged. It happens that Github has a good set of tools for this, but if you decided that on date X you wanted to move away I don't think it would be that hard to shift away. You'd have the same mandate about code review, you just point people at a different tool set to do it.

kanox 6y ago

Email archives are even harder to transfer, and to make sense of in general. For example if you want to find the review comment thread for linux commits there is no reliable way to do it, your best bet is to google the title.

angio 6y ago
> Email archives are even harder to transfer, and to make sense of in general. Email archives are very easy to transfer, you simply download the mbox file from the old system and import them to the new one [0]. > For example if you want to find the review comment thread for linux commits there is no reliable way to do it, your best bet is to google the title. In my experience, projects that use a ml-based workflow have higher standards for commit messages and so the information about a commit is usually in the commit. [0] https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archi...
Seirdy 6y ago
> Email archives are even harder to transfer Mailing lists are trivial to distribute. Thanks to maildir and mbox, everybody has a full copy of the mailing list just as they have a full copy of the repository.
- kanox 6y ago
  > Thanks to maildir and mbox, everybody has a full copy of the mailing list. No, that only covers emails that you personally received. You need another mechanism for older emails.
  - ddevault 6y ago
    A mechanism which is provided by mailing list archives in the form of mbox downloads. If you question the reliability of this (but apparently not the proven unreliability of GitHub), as a fallback you can just ask an older subscriber to give you their mbox.