[AppStream] <suggests>

[Lucas Moura]

Hello,

No problem, I will start working on this new component type today. However,
the merge now should only occur if a component providing the additional
data is of type "merge", right ? I am asking that just to implement the
correct behavior on the as-data-pool merge method.

And about the GSOC students, hahahah, there is actually just me and another
student. I am working with AppStream and trying to improve AppRecommender
package while also improving some other stuff on the AppRecommender code as
well. The other student is working on creating the new AppRecommender
strategy and on the issues of using popularity-contest data for
recommendation purposes.

Cheers,
Lucas Moura

On Thu, Jul 28, 2016 at 11:30 AM, Matthias Klumpp <matthias at tenstral.net>
wrote:

> 2016-07-28 16:17 GMT+02:00 Lucas Moura <lucas.moura128 at gmail.com>:
> > Hello,
> >
> > No problem for me. I think the other GSOC student will start working on
> this
> > new strategy this week. Therefore, I can keep in touch with him about
> this
> > feature on AppStream.
>
> That's great, TBH I think the suggests feature in the normal metadata
> is the much better approach to this issue (and - actually a bit more
> important - it also is the more maintainable approach long-term).
>
> In order for this to work for you, we will also need the
> fake-component-type "merge" (or "partial" or whatever we come up with,
> but I think "merge" isn't so bad) in order to augment the data of
> existing components.
>
> Cheers,
>     Matthias
>
> P.S: There's another GSoC student? How many are working on this? :D
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/appstream/attachments/20160729/8957e866/attachment.html>