The Teamboard: Difference between revisions
(remove loomio stuff) |
|||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
- Mentions in comments ([https://github.com/diaspora/diaspora/issues/1851 #1851]) | - Mentions in comments ([https://github.com/diaspora/diaspora/issues/1851 #1851]) | ||
- Embed direct links to HTML5 media in <audio> / <video> tags ([https://github.com/diaspora/diaspora/issues/4601 #4601]) | |||
- Federation behavior testing | - Federation behavior testing | ||
==== Maintainers' reaction required ==== | ==== Maintainers' reaction required ==== | ||
- Extend the generated fixtures set and refactor AccountDeletion ([https://github.com/diaspora/diaspora/pull/6783#discussion-diff-60526640 #6783]) | - Extend the generated fixtures set and refactor AccountDeletion ([https://github.com/diaspora/diaspora/pull/6783#discussion-diff-60526640 #6783]) | ||
- Update the user data export archive format. ([https://github.com/diaspora/diaspora/pull/6726#issuecomment-219322202 #6726]) | - <strike>Update the user data export archive format. ([https://github.com/diaspora/diaspora/pull/6726#issuecomment-219322202 #6726])</strike> | ||
==== Account backup/migration plan ==== | ==== Account backup/migration plan ==== | ||
see [https://gist.github.com/cmrd-senya/1530eca8bb208e6324829a708ea07032 spec] | |||
Archive schema updates are WIP. [https://discourse.diasporafoundation.org/t/backup-and-restore/544/91 Discussion] regarding inclusion of polls to the user's archive. | |||
==== Mentions in comments ==== | ==== Mentions in comments ==== | ||
| Line 29: | Line 27: | ||
I started [https://github.com/cmrd-senya/diaspora_federation_behavior this] project in order to make federation testing possible in a reproducible way and as close as possible to the real pod data exchange. This package includes rake tasks that deploy a number of test pods basing on [https://github.com/joebew42/diaspora-replica diaspora-replica] and LXC. Then it communicates with the pods using JSON requests with the [https://github.com/cmrd-senya/diaspora-api diaspora-api] gem and perform actions which imply data exchange using the federation routines. This tool may help in debugging federation refactorings, new features development, regression testings against new and old code. I was provided with a server and I'm now going to deploy the software using the buildbot as a CI system. | I started [https://github.com/cmrd-senya/diaspora_federation_behavior this] project in order to make federation testing possible in a reproducible way and as close as possible to the real pod data exchange. This package includes rake tasks that deploy a number of test pods basing on [https://github.com/joebew42/diaspora-replica diaspora-replica] and LXC. Then it communicates with the pods using JSON requests with the [https://github.com/cmrd-senya/diaspora-api diaspora-api] gem and perform actions which imply data exchange using the federation routines. This tool may help in debugging federation refactorings, new features development, regression testings against new and old code. I was provided with a server and I'm now going to deploy the software using the buildbot as a CI system. | ||
[http://190.15.209.124:8010/grid CI deployed!] | |||
'''Short explanations''' | |||
If you take a look on the grid page, you’ll see the three rows in the table (besides the header). In the left column there are so called “builders” which are in fact are the different test sets. All the tests are parts of the “diaspora_federation_behavior” which runs a couple of test pods and drives them with the client API and verifies that the data gets federated well. | |||
“known_federation_bugs” is made for bugs that are present in the federation right now. That why it’s red - these test (well, only one ATM) fail now. | |||
“regression_testing” is section for current federation features and it is made to control that nothing was broken in the new updates. | |||
There is also the “rename_feature” section that uses my feature branch for the account migration step 1 and tests whether the account rename goes well across the federation. There are few tests yet, but that could be used as a framework for much more cool things which could, I believe, help diaspora project to stay stable. | |||
=== Fla (Flaburgan) === | === Fla (Flaburgan) === | ||
| Line 38: | Line 46: | ||
- Add links to liked and commented pages PR: [https://github.com/diaspora/diaspora/pull/5502 #5502] [WIP] (A painful rebase is needed, I have to work on it) | - Add links to liked and commented pages PR: [https://github.com/diaspora/diaspora/pull/5502 #5502] [WIP] (A painful rebase is needed, I have to work on it) | ||
[[Category:Community]] | |||
[[Category:Developers]] | |||
Latest revision as of 22:57, 30 August 2017
This page is proposed to be used to have the summarized status of contributors present work.
Contributors
Senya
Issues in hand
- Account backup/migration (#908)
- Mentions in comments (#1851)
- Embed direct links to HTML5 media in <audio> / <video> tags (#4601)
- Federation behavior testing
Maintainers' reaction required
- Extend the generated fixtures set and refactor AccountDeletion (#6783)
- Update the user data export archive format. (#6726)
Account backup/migration plan
see spec
Archive schema updates are WIP. Discussion regarding inclusion of polls to the user's archive.
Mentions in comments
I started this work in #6818. It must be decided, whether it worth doing anything about the issue before the new federation code gets integrated or not.
Federation behavior testing
I started this project in order to make federation testing possible in a reproducible way and as close as possible to the real pod data exchange. This package includes rake tasks that deploy a number of test pods basing on diaspora-replica and LXC. Then it communicates with the pods using JSON requests with the diaspora-api gem and perform actions which imply data exchange using the federation routines. This tool may help in debugging federation refactorings, new features development, regression testings against new and old code. I was provided with a server and I'm now going to deploy the software using the buildbot as a CI system.
Short explanations If you take a look on the grid page, you’ll see the three rows in the table (besides the header). In the left column there are so called “builders” which are in fact are the different test sets. All the tests are parts of the “diaspora_federation_behavior” which runs a couple of test pods and drives them with the client API and verifies that the data gets federated well.
“known_federation_bugs” is made for bugs that are present in the federation right now. That why it’s red - these test (well, only one ATM) fail now.
“regression_testing” is section for current federation features and it is made to control that nothing was broken in the new updates.
There is also the “rename_feature” section that uses my feature branch for the account migration step 1 and tests whether the account rename goes well across the federation. There are few tests yet, but that could be used as a framework for much more cool things which could, I believe, help diaspora project to stay stable.
Fla (Flaburgan)
Issues in hand
- Photos - CSS floats causes ugly spaces when using different image sizes #6809. PR: #6838 [TO BE REVIEWED]
- Poll display "1 vote" when 0% #6835 [WIP]
- Add links to liked and commented pages PR: #5502 [WIP] (A painful rebase is needed, I have to work on it)