Imported from previous forum
[ original email was from John Harris - john.harris@bondmart.com ]
As discussed on our call this morning, I would like to see this group try an open wiki to help with the process of documenting requirements, which is the next task at hand.
My proposal is as follows:
-
Allow and encourage anyone to edit.
-
Give administrative control to multiple, trusted people, so that profanity, spam, vandalism, etc. can be quickly caught and remedied.
-
Implement moderated edit rights if dealing with miscreants becomes too time-consuming.
-
Locate the wiki within the fixprotocol.org domain.
If that isn’t agreeable, then I would propose to set one up myself and request permission to post the URL within the discussion forum (without accusations of spamming). I would do so under Creative Commons license and pledge the content in advance to FPL.
[ original email was from John Harris - john.harris@bondmart.com ]
Further to this post, I promised to post an example of a protocol that is being organized through a wiki. The one I had in mind is dot-p2p, which is a new, peer-to-peer DNS:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめ
It does get spammed. Here is its pages list:
But it also is used. Some stats:
As discussed on our call this morning, I would like to see this group try an open wiki to help with the process of documenting requirements, which is the next task at hand.
My proposal is as follows:
Allow and encourage anyone to edit.
Give administrative control to multiple, trusted people, so that profanity, spam, vandalism, etc. can be quickly caught and remedied.
Implement moderated edit rights if dealing with miscreants becomes too time-consuming.
Locate the wiki within the fixprotocol.org domain.
If that isn’t agreeable, then I would propose to set one up myself and request permission to post the URL within the discussion forum (without accusations of spamming). I would do so under Creative Commons license and pledge the content in advance to FPL.
Hi John,
I sent an account request for the newly released FIXwiki at
http://fixwiki.fixprotocol.org/fixwiki/FIXwiki
and the request was SLR’ed with text
"Sorry, your request for an account “Mahesh Kumaraguru” has been rejected on FIXwiki.
Account requests are granted only to those who are employees of a FPL member institution in good standing."
So you may have to try getting a HFTwiki setup which does NOT have this “member firm employee” restriction and ideas can flourish. When an official partcipation factor comes in, participants would have their own reservations about posting ideas on the wiki without first getting official approval - why embarress the employer ? or what if employer gets upset and takes some disciplinary action ?
Setting up a HFTwiki like http://FIXProtocol.org/hftwiki should not be a big deal, but if its getting delayed / too much red tape to cut thru, then lets just proceed with using this discussion board for sharing ideas and emails for documents sharing - the time tested and already available tools 
I am more than happy to help with any moderation / spam prevention / admin work in a new wiki.
Regards,
K. Mahesh
Further to this post, I promised to post an example of a protocol that is being organized through a wiki. The one I had in mind is dot-p2p, which is a new, peer-to-peer DNS:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめIt does get spammed. Here is its pages list:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめBut it also is used. Some stats:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめAs discussed on our call this morning, I would like to see this group try an open wiki to help with the process of documenting requirements, which is the next task at hand.
My proposal is as follows:
Allow and encourage anyone to edit.
Give administrative control to multiple, trusted people, so that profanity, spam, vandalism, etc. can be quickly caught and remedied.
Implement moderated edit rights if dealing with miscreants becomes too time-consuming.
Locate the wiki within the fixprotocol.org domain.
If that isn’t agreeable, then I would propose to set one up myself and request permission to post the URL within the discussion forum (without accusations of spamming). I would do so under Creative Commons license and pledge the content in advance to FPL.
[ original email was from John Harris - john.harris@bondmart.com ]
Mahesh,
As a contributor to the effort, I would like to try an open wiki as a development tool for the new protocol (while freely admitting that it may prove impractical or unproductive). My understanding is that participants generally supported the idea of open participation - and an open wiki - at the first meeting of what is now the High Performance Interface Working Group. In order to be as successful as possible, an undertaking such as this has to seek ideas and help from all over the world; it has to be open to experimentation and failure; it has to challenge pre-conceived notions. At the same time, it has to have some organization to it, though that organization needn’t be centrally coordinated or hierarchical.
I have some strong opinions - not necessarily correct ones - about how I would like to see FIX evolve. Others have better ideas than I. I am certain there are people who have never even heard of FIX who could and would make terrific contributions to the effort, if only given the chance.
Hopefully we can have an open wiki at fixprotocol.org. That would be best. If that’s not possible, we can settle for second best.
Best,
John
Hi John,
I sent an account request for the newly released FIXwiki at
http://fixwiki.fixprotocol.org/fixwiki/FIXwiki
and the request was SLR’ed with text
"Sorry, your request for an account “Mahesh Kumaraguru” has been rejected on FIXwiki.
Account requests are granted only to those who are employees of a FPL member institution in good standing."
So you may have to try getting a HFTwiki setup which does NOT have this “member firm employee” restriction and ideas can flourish. When an official partcipation factor comes in, participants would have their own reservations about posting ideas on the wiki without first getting official approval - why embarress the employer ? or what if employer gets upset and takes some disciplinary action ?
Setting up a HFTwiki like http://FIXProtocol.org/hftwiki should not be a big deal, but if its getting delayed / too much red tape to cut thru, then lets just proceed with using this discussion board for sharing ideas and emails for documents sharing - the time tested and already available tools
Regards,
K. MaheshFurther to this post, I promised to post an example of a protocol that is being organized through a wiki. The one I had in mind is dot-p2p, which is a new, peer-to-peer DNS:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめIt does get spammed. Here is its pages list:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめBut it also is used. Some stats:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめAs discussed on our call this morning, I would like to see this group try an open wiki to help with the process of documenting requirements, which is the next task at hand.
My proposal is as follows:
Allow and encourage anyone to edit.
Give administrative control to multiple, trusted people, so that profanity, spam, vandalism, etc. can be quickly caught and remedied.
Implement moderated edit rights if dealing with miscreants becomes too time-consuming.
Locate the wiki within the fixprotocol.org domain.
If that isn’t agreeable, then I would propose to set one up myself and request permission to post the URL within the discussion forum (without accusations of spamming). I would do so under Creative Commons license and pledge the content in advance to FPL.
Mahesh,
the FIXwiki currently has no direct relationship to the HPIwg (or any other wg afaik). This may change in the future but it has not been discussed to my knowledge.
FIXwiki accounts are only granted for users that are affiliated with an FPL member. One alternative for you is to apply for FPL membership. Another alternative is to get affiliated with a member firm.
Best,
Rolf
Hi John,
I sent an account request for the newly released FIXwiki at
http://fixwiki.fixprotocol.org/fixwiki/FIXwiki
and the request was SLR’ed with text
"Sorry, your request for an account “Mahesh Kumaraguru” has been rejected on FIXwiki.
Account requests are granted only to those who are employees of a FPL member institution in good standing."
So you may have to try getting a HFTwiki setup which does NOT have this “member firm employee” restriction and ideas can flourish. When an official partcipation factor comes in, participants would have their own reservations about posting ideas on the wiki without first getting official approval - why embarress the employer ? or what if employer gets upset and takes some disciplinary action ?
Setting up a HFTwiki like http://FIXProtocol.org/hftwiki should not be a big deal, but if its getting delayed / too much red tape to cut thru, then lets just proceed with using this discussion board for sharing ideas and emails for documents sharing - the time tested and already available tools
Regards,
K. Mahesh
John, having spent some time reviewing the dot-p2p.org wiki I remain unconvinced. There is little focus, a fair amount of random comments and some outright spam.
You are obviously free to try it outside of the FPL.
I’m voting against this arrangement for the HPIwg.
/Rolf
Further to this post, I promised to post an example of a protocol that is being organized through a wiki. The one I had in mind is dot-p2p, which is a new, peer-to-peer DNS:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめIt does get spammed. Here is its pages list:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめBut it also is used. Some stats:
元金欠保育士の副業まとめ | 副業の口コミ、評判を徹底調査｜元金欠保育士の副業まとめAs discussed on our call this morning, I would like to see this group try an open wiki to help with the process of documenting requirements, which is the next task at hand.
My proposal is as follows:
Allow and encourage anyone to edit.
Give administrative control to multiple, trusted people, so that profanity, spam, vandalism, etc. can be quickly caught and remedied.
Implement moderated edit rights if dealing with miscreants becomes too time-consuming.
Locate the wiki within the fixprotocol.org domain.
If that isn’t agreeable, then I would propose to set one up myself and request permission to post the URL within the discussion forum (without accusations of spamming). I would do so under Creative Commons license and pledge the content in advance to FPL.