Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Roadmap #315

Merged
merged 4 commits into from Jan 29, 2019
Merged

Add Roadmap #315

merged 4 commits into from Jan 29, 2019

Conversation

cblanco
Copy link
Contributor

@cblanco cblanco commented Jan 28, 2019

No description provided.


- Support for geospatial analysis (geo-fencing, point-based actions, movement-based actions)

- Enhanced multi-tenancy support. Leverage different “Fiware-Service” and “Fiware-ServicePath” in rules
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to use straitgh quotes "..." instead that “...”

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in da7e1dc

## Introduction

This section elaborates on proposed new features or tasks which are expected to be added to the product in the foreseeable future. There should be no assumption of a commitment to deliver these features on specific dates or in the order given. The development team will be doing their best to follow the proposed dates and priorities, but please bear in mind that plans to work on a given feature or task may be revised. All information is provided as a general guidelines only, and this section may be revised to provide newer information at any time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could add also the following disclaimer (https://github.com/telefonicaid/fiware-orion/blob/master/doc/roadmap.md#introduction):

  • This section has been last updated in January 2019. Please take into account its content could be obsolete.
  • Note we develop this software in Agile way, so development plan is continuously under review. Thus, this roadmap has to be understood as rough plan of features to be done along time which is fully valid only at the time of writing it. This roadmap has not be understood as a commitment on features and/or dates.
  • Some of the roadmap items may be implemented by external community developers, out of the scope of GEi owners. Thus, the moment in which these features will be finalized cannot be assured.

Up to you :). If you prefer not adding it and keep it as it is now, then NTC on this comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 8a43e97

@fgalan
Copy link
Member

fgalan commented Jan 28, 2019

Some possible additions:

  • Rule auto-naming on rule creation time (I think we discussed this in the past, although maybe is too minor to be included in a roadmap). Or it was already done? (not remember at this moment, sorry)
  • Description API in OpenAPIv3 (I think we also mentioned this in the past)
  • Rule templates (i.e. having a rule template that can be instanciated to create particular instances of the rule). This can be useful for rules with complex EPL, so the EPL is provide just one time (in the template), then each instance of rule based on that template only provides the specific information for that.

Just in case you want to consider adding them (maybe in the lont term stage).

@cblanco
Copy link
Contributor Author

cblanco commented Jan 28, 2019

Some possible additions:

  • Rule auto-naming on rule creation time (I think we discussed this in the past, although maybe is too minor to be included in a roadmap). Or it was already done? (not remember at this moment, sorry)

I don't know if you are referring the feature added by PR #316. In the current roadmap file, you can see the description of this feature in the line number 21.

  • Description API in OpenAPIv3 (I think we also mentioned this in the past)

Ok. We have an initial version here. I will try to make a PR as soon as possible.
Fixed in 7adf4c6

  • Rule templates (i.e. having a rule template that can be instanciated to create particular instances of the rule). This can be useful for rules with complex EPL, so the EPL is provide just one time (in the template), then each instance of rule based on that template only provides the specific information for that.

Just in case you want to consider adding them (maybe in the lont term stage).

Ok. Fixed in 7adf4c6

Copy link
Member

@fgalan fgalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@fgalan fgalan merged commit 5f4372e into telefonicaid:master Jan 29, 2019
@cblanco cblanco deleted the feature/roadmap branch February 1, 2019 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants