Currently, there are a lot of hardcoded texts on the website. We need to get them translations in a.s.a.p., before it's too late and we speak english forever and ever and ever...

We'd like some newer software (Debian Stretch, MariaDB 10.1, PHP7.1)

We have PHPspec specifications now, and running them in Travis is a requirement.

We would like contributors to talk a little about what they have learned - no matter how small - while working on Elewant.

Twitter gives location information that we can use as a basic value for a Herd location. It probably For Herds, we will use Lat/Long later.

An experiment, to learn what we can gain by using mutation testing. Since we have zero experience with Humbug or even mutation testing, just adding the testing framework with a single test would be good enough for a merge.

https://github.com/humbug/humbug

Except for the inline javascript. There's a (placeholder) file src/Elewant/FrontendBundle/Resources/assets/js/elewant.js, which is (emtpy, but) already used in Grunt. So I'd suggest to bind the events to to proper classes 🙂
Also, we have jQuery, so no need to manually build anXMLHttpRequest 😉

An experiment, to learn what we can gain by using static analysis

We need to actually have them, or remove the links on the template.
If we have them, it should be super simple and plain: no data is ever going to be sold. We only use your data to provide the service. Anyone can use this site.

We can use a single page that contains all the possible elements available to build pages on the website.

That gives us as a visual method of choosing the right "component" for a certain use case, as well as example-html.

Two elePHPants breeds are missing! They are noted as "related species" in the field guide, so they where not added in the initial list.

Please add Woolly Mammoth and pHackyderm.

A Herd does not have a location. In order to show herds on a map, we want to add a lat/long to a Herd's properties.

The "relocate herd" command can be run for all existing users by making a (console) command that takes the "country" input from Twitter and transforms that into lat/long.

After that, we should have a user-interface for changing the location of your herd, preferably on a map (resulting in lat/long coordinates).

A cool idea: for any Herds that we don't have a location for, just show them on a random place on the map with a question mark and a message to the user "Your herd is lost... help guiding them home!"

The Herding domain works with a ShepherdId (uuid) to form new herds. Every new registered used will have their own herd - just one - based on their ShepherdId.

A Shepherd is the master of their Herd. If they wish to give up one (or more) of their Herd for adoption, they will trigger a GiveUpForAdoption command.

• The ElePHPant is still part of the Herd, but no longer available for abandonment (the possibility for adoption must first be cancelled)
• There might be more information required before this ElePHPant is properly available for trade, like: quality, in which actual batch it was created, location...
• Quite possible this means the addition of the \Elewant\Trading domain in the code.

The template images have all been added to the source. All unused images can be removed.

Some images need to be replaced with our own photo's of ElePHPants - we need to do a photoshoot!

Due to the single page template the navbar links scroll smoothly to the area they link to.

But on different pages (in this case /herd/tending or /shepherd/[username]) the links do not point to anything on the page.

This needs to be looked at.

https://waffle.io/f500/elewant

Add 404 and 500 views

We have an SSL certificate for elewant.com, but it would be nice to have an ansible role in provisioning to use LetsEncrypt for this project.

Give people a place to notify us privately when they find security issues. This could be as simple as an email address, but let's be explicit about it.

A map that shows all the herds.

Probably a good idea to use http://leafletjs.com and openstreetmap.

Since our application can only login with Twitter, we want a button that visitors can press to let us know If they have no twitter.

For Developers, being able to log in should not be connected to Twitter (they won't have our application codes) so a basic existing user could be added to the fixtures to allow a developer to log in without actual twitter login.

(this can then be extended to a production registration/login process without Twitter, but that is a separate issue)

When chosing which ElePHPants I have, it becomes quite difficult without knowing which different ones actually exist (there are three blue ones for example)

Add a supporting text and a link to http://afieldguidetoelephpants.net/ in the Herd adoption modal.

Install symfony2 and created 1 bundle for now

With Herd management, the ElePHPants overlap when on a smaller screen. This needs some love and attention for all screen sizes.

Instead of the current input type of text, we should have a list of countries.
If the value received from Twitter is in the list, it is automatically preselected.

When a user joins Elewant, we agreed on automatically forming a new herd for every user to simplify the initial application.

This change proposes a processmanager that can respond to events with new commands. The command in this case being formAHerd whenever a newUserHasRegistered.
(note that at this point, both the command and the event do not exist yet)

Since we're using the Prooph event-sourcing library, we should also implement Prooph event-store.

We like to use this theme:
https://startbootstrap.com/template-overviews/grayscale/

Let's go Bootstrap 4, hook it up with Grunt (npm & bower) for now.

Tasks to be done before we can mark this as done:

• Set up npm and grunt, enabling the theme.
• Split the theme up in usable view files.
• Integrate current views with the theme (user registration).

When visiting an existing Herd, the page will display the name of the Herd, and all it's ElePHPants.

Currently, the /shepherd/{username} find a Herd not by searching for a User with user::username, but by querying for a Herd with herd::name instead.

This solves the problem of creating links to these shepherd pages in places where we only have access to a Herd, like the "newest Herds list". But it would also be the case in a search page.
So "create a link to the public page of this herd" in a view is a difficult problem if the Herd does not know the shepherds name but only the shepherdId.

Using the Herd::name is a workaround for now because we automatically create a herd with the same name as the user on registration, but this would break in the future if we allow a "rename herd" command or if we implement multiple herds per shepherd.

The proposed solution is to add a shepherd_name column and a shepherdName property to the Herd read model (the Herd entity in the AppBundle). The data would be filled by the herd projection - meaning we don't have to change the events but just rebuild the read model with the new projection in place. There are console commands that can do that.

In the "newest herd" list there are breed names, but it would be nicer to see an actual colored elephpant. All ElePHPants in the herd could be shown in a grid instead of the name in text.

A Shepherd can maintain a list of ElePHPants that they would like to add to their Herd.

A place to put the last 5 added Herds on the front page

We currently have a single domain called Herding, with a DomeinModel.md file describing it. When we start adding other domains (like Trading), we want to be able to link to a general glossary to cover words that exist in the entire bounded context.

After successful registration, a new Herd is automatically formed for the user, with the Twitter username as the name for their Herd.

Once the registration is completed, the user is redirected to an edit page for an empty herd - displaying all Breeds of ElePHPants and the option to add them to the new herd.

After completion, the user is redirected to their own public Herd listing, displaying the name of the herd (the Twitter username) and the collection of ElePHPants that they have.

The /shepherd/{username} page can use a search bar where you can search for other shepherd names.

Until we solve #68 this would actually search for Herd::name, but that should not be a problem right now.

Some people might own ElePHPants, but not want to display them publicly. Do we need to add a feature that "hides" ElePHPants from public view, and if so - is that part of the domain model or is that a read model thing.

The unit tests don't need to use $this to assert things. In order to reduce confusion between PHPspec specs and PHPUnit tests we can remove $this from the latter:

TestCase::assertEquals(202, $this->client->getResponse()->getStatusCode());

In favor of:

$this->assertEquals(202, $this->client->getResponse()->getStatusCode());

Users should be able to login with there twitter accounts.

Some information about Elewant's purpose and creators on an About page.

Once a Herd is formed and contains ElePHPants, the Herd can be changed by the Shepherd.

The view for this shows all the ElePHPant Breeds in the Herd, with a "+" and a "-" sign to add or remove. There is also a method to add a new Breed to the Herd, though a list of all Breeds and an "adopt" button.

Every breed has a translation, that currently requires you to concat a string in the view (which is a pain):

("herding.breed." ~ breed)|trans

We should try to In order to make those translations more easy to use.
Putting them in their own translation domain could help.. or a special transBreed filter for Twig that abstracts the additional string concatination...

The colors used for the ElePHPants can use a tripple-check

Twitter account should saved so we can make relations in the database.

There should be a extra property "is_organization" to define if the user account is an organization (that mostly sell elephpants).

On behalf of users when they complete their first Herd: "I just added my Herd of 7 elephpants on Elewant.com! Will you?"

Currently, we do not ask for the required permission to post tweets for users.

The website and the Twitter account need some nice ElePHPant visuals... Plus: Stickerz :D

Currently, the Herd and ElePHPant models both use a DateTime type for formedOn and adoptedOn respectively.

The precision of these times can be limited to seconds, because that is the most precise value the domain is interested in. This means creating value objects that disregard the microseconds.

It also warrants the creation of a system clock that can be used to retrieve the system time.

See http://rosstuck.com/precision-through-imprecision-improving-time-objects