>Transaction ID should be derived from all the contentof the TX (including nonce, args, cert, etc.) On the whole, I agree with this approach. To recap the motivation original implementation generated

From what I've seen the #fabric channelhas been used for newbies, with #fabric-dev and #fabric-dev-env being usedmore for development discussions. I think it would make sense to keep themailing lists

For me, it seems that we were unable to achieve a consensus in the public in this topic, yet. Now, I would like start a new discussion with a little bit reworked proposal: Transaction ID should be

I had a look at the two Wikis (Media, Doku, http://www.wikimatrix.org/compare/dokuwiki+mediawiki and some example wikis), MediaWiki seems to be a little bit better, but I think the ultimate solution

Cc'ing Ry in case he's not on the list. Is there any way in the GH admin console we can just turn off new issues? If not, we could modify the template for new issues on GH to even

Correction: still visible, but not editable, which is just as bad. Let's get input by the end of the week then. I have also discovered we can add Confluence to the list of wiki

And finally a comment on this :) I think it's acceptable to close issues on GH with "please open a new issue at jira.hyperledger.org if this issue still persists", so long as: a) Fabric developers

I don't have a preference, but we do have a need to relocate the Fabric wiki as it is no longer available. Thanks, - Binh Brian Behlendorf ---08/08/2016 06:54:57 PM---For the time being we can

Hi All I propose we close all existing pull requests at https://github.com/hyperledger/fabric/pulls soon. We should then create a single pull request similar to the one at

For the time being we can continue using the Github wiki, but to make the migration complete we should talk about setting up a separate wiki tool for the Hyperledger projects.

And for clarity, you can create that account at http://identity.linuxfoundation.org/ Sadly, browser auto-fill or password database tools won't pick up the name/password combo the first

Thanks, I understood that Jira will replace Github issue as well as Gerrit replaced Github Repository. How about Github wiki? Do you have any plan to migrate wiki documents elsewhere? Best

Jira issues replace the role of GitHub issues. Just a different tool - one that allows greater flexibility than GH. If you find a bug, submit a Jira issue and if you are interested, you can also

Hello Chris. May I ask questions? 1) Process of issue discussion and bug fix Currently, contributors submit issue/bug to Gerrit directly and reviewers check it. How this process will change

+1 For the fresh start but I also agree with Arnaud's idea that we should try not to lose any important issue that is worth moving. :) -- GABOR HOSSZU ​DEVELOPER +​36 1 883 0300

+1 what Ry said, your LF credentials should work Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Technology IBM Cloud, Open Technologies email: chrisfer@... twitter:

The same credentials are used across any LF-managed property except the mailing list manager, so the same credentials should work on gerrit.hyperledger.org, jenkins.hyperledger.org, and

What login should be used for that JIRA instance, Chris? My hyperledger.org credentials don't seem to work. Should they? How many different logins are required for a Hyperledger participant to use

+1. I already had a go at trying to enliven a bunch of stale issues. We can use that as a baseline. If no activity after a week of Jira, then we can close them. We might want to look at trying to

I support the fresh start but I think itwould make sense to have a look after a while and see if we lost anythingthat might be worth moving over because the person who initially raisedthe issue on